relocation of mobility and access management (amf) function in a change triggered by network of netw

专利摘要:
these are methods, systems and devices for wireless communication. a method may include determining to modify the currently allowed network slices used by a user device (eu) based on a network trigger; identify newly allowed network slices for the eu based on the determination; select a target mobility and access management (amf) function based on the recently allowed network slices, the target amf is accessible by the source amf; and trigger an amf relocation based on selection.
公开号:BR112019023498A2
申请号:R112019023498
申请日:2018-04-27
公开日:2020-05-19
发明作者:Genevieve Chaponniere Lenaig；Faccin Stefano
申请人:Qualcomm Inc；
IPC主号:

专利说明:

RE LOCATION OF MOBILITY AND ACCESS (AMF) MANAGEMENT FUNCTION IN A CHANGE UNDERTAKEN BY NETWORK OF
NETWORK SLICES SUPPORTED BY USER EQUIPMENT
CROSS REFERENCES
[0001] The present Patent Application claims the benefit of Patent Application No. US 15 / 963,654 by FACCIN, et al., Entitled ENABLE A NETWORKTRIGGER CHANGE OF NETWORK SLICES, filed on April 26, 2018; and Provisional Patent Application No. US 62 / 505,904 by FACCIN, et al., entitled ENABLE A NETWORKTRIGGER CHANGE CF NETWORK SLICES, filed on May 13, 2017; each of which is assigned to the assignee.
INTRODUCTION
[0002] The following refers, generally, to wireless communication and, more specifically, to enable a change of network triggering of network slices.
[0003] Wireless communications systems are widely installed to provide various types of communication content such as voice, video, data packets, messages, broadcast, and so on. These systems may be able to support communication with multiple users by sharing available system resources (for example, time, frequency and power). Examples of such multiple access systems include code division multiple access systems (CDMA), time division multiple access systems (TDMA), frequency division multiple access systems (FDMA) and division multiple access systems in
Petition 870190114669, of 11/08/2019, p. 6/172
2/117 orthogonal frequency (OFDMA), (for example, a Long Term Evolution (LTE) system or a New Radio (NR) system). A wireless multiple access communications system can include numerous base stations or access network nodes, each simultaneously supporting communication to multiple communication devices, which may otherwise be known as user equipment (UE) . In some examples, of wireless communication systems, an UE may use one or more network slices. A network slice is a logical network that includes Radio Access Network (RAN) and Main Network (CN). A network slice provides network services and capabilities, which can vary or be the same network slice for the network slice. A UE can access multiple network slices simultaneously through an RAN.
SUMMARY
[0004] A method for wireless communication in a source mobility and access management (AMF) function is described. The method may include determining whether to modify currently allowed network slices supported for a UE based at least in part on a network trigger; identify recently allowed network slices supported for the UE based at least in part on the determination; select a target AMF based at least in part on the recently allowed network slices, AMFalvo is accessible by the source AMF; and trigger an MFA relocation based at least in part on selection.
[0005] A device for wireless communication is described. The apparatus may include means for determining which
Petition 870190114669, of 11/08/2019, p. 7/172
3/117 if currently allowed network slices supported for a UE are modified based at least in part on a network trigger; means for identifying recently allowed network slices supported for the UE based at least in part on the determination; means for selecting a target AMF based at least in part on the recently allowed network slices, the target AMF is accessible through the AMF source; and means for triggering an MFA relocation based at least in part on selection.
[0006] Another device for wireless communication is described. The device may include a processor, memory in electronic communication with the processor. The processor and memory can be configured to determine that currently allowed network slices supported for a UE are modified based at least in part on a network trigger; identify recently allowed network slices supported for the UE based at least in part on the determination; select a target AMF based at least in part on the recently allowed network slices, the target AMF is accessible by the source AMF; and trigger an MFA relocation based at least in part on selection.
[0007] A non-transitory, computer-readable medium for wireless communication is described. The non-transitory computer-readable medium may include operable instructions to cause a processor to determine which currently permitted network slices supported for a UE are modified based at least in part on a network trigger; identify recently allowed network slices supported for the UE based on the
Petition 870190114669, of 11/08/2019, p. 8/172
4/117 less in part in the determination; select a target AMF based at least in part on the recently allowed network slices, the target AMF is accessible by the source AMF; and trigger an MFA relocation based at least in part on selection.
[0008] Some examples of the non-transitory computer-readable method, apparatus and medium described above may additionally include processes, resources, means or instructions to determine that the UE has an active network slice (NSI) instance associated with at least one piece of information network selection assistance (NSSAI); and identifying that an active NSI is supported by the recently allowed network slices. Some examples of the non-transitory, computer-readable method, apparatus and medium described above may additionally include processes, resources, means or instructions for generating a progress report that indicates a status of all associated existing protocol data unit (PDU) sessions to the active NSI.
[0009] Some examples of the non-transitory, computer-readable method, apparatus and medium described above for triggering MFA relocation may additionally include processes, resources, means or instructions for transmitting an MFA relocation request to the target AMF based on the less in part in the recently permitted NSSAI, the AMF relocation request comprises a status of all existing PDU sessions associated with the active NSI that are supported and active, or a new radio (NR) globally unique temporary identifier (GUTI), or both.
Petition 870190114669, of 11/08/2019, p. 9/172
5/117
[0010] Some examples of the non-transitory computer-readable method, apparatus and medium described may additionally include processes, resources, means or instructions to trigger the procedure for releasing an active PDU session associated with the currently allowed network slices based on at least partly in identifying that the active PDU session is not supported by the recently allowed network slices. In some examples of the non-transitory computer-readable method, apparatus and medium described above, the triggering of the release procedure is based at least in part on direct signaling to the UE.
[0011] Another method for wireless communication on a target AMF is described. The method may include receiving, from an AMF source, an AMF relocation request to an UE currently served by the source AMF, the AMF relocation request comprising recently allowed network slices and UE context information; allocate an updated identifier based at least in part on the AMF relocation request; and transmitting to the UE a configuration request message comprising the updated identifier, an updated status of an existing PDU session, or the recently allowed network slices, or a combination.
[0012] Another device for wireless communication is described. The apparatus may include means for receiving an AMF relocation request from a source network entity to a UE currently served by the source network entity, the AMF relocation request comprising network slices recently.
Petition 870190114669, of 11/08/2019, p. 10/172
6/117 allowed and EU context information; means for allocating an updated identifier based at least in part on the AMF relocation request; and means for transmitting a configuration request message to the UE comprising the updated identifier, an updated status of an existing PDU session, or the recently allowed network slices, or a combination.
[0013] Another device for wireless communication is described. The device may include a processor, memory in electronic communication with the processor. The processor and memory can be configured to receive an AMF relocation request for an UE currently served by a source AMF, the AMF relocation request comprising recently allowed network slices and UE context information; allocate an updated identifier based at least in part on the AMF relocation request; and transmitting to the UE a configuration request message comprising the updated identifier, an updated status of an existing PDU session, or the recently allowed network slices, or a combination.
[0014] Another non-transitory, computer-readable means for wireless communication is described. The non-transitory computer-readable medium may include operable instructions to have a processor receive an AMF relocation request for an UE currently served by an AMF source, with the AMF relocation request comprising recently allowed network slices and EU context information; allocate an updated identifier based on at least
Petition 870190114669, of 11/08/2019, p. 11/172
7/117 partly in the request for relocation of MFA; and transmit a configuration request message to the UE comprising the updated identifier, an updated status of an existing PDU session, or the recently allowed network slices, or a combination.
[0015] In some examples of the non-transitory computer-readable method, device and medium described above, the updated identifier comprises NR GUTI. In some examples of the non-transitory computer-readable method, apparatus and medium described above, where the UE context information comprises a situation of an existing PDU session associated with an active NSI or a current NR GUTI, or combination.
[0016] Another method for wireless communication in an UE is described. The method may include receiving, from a source AMF, a configuration message comprising an identifier associated with a target AMF, a situation of existing active PDU sessions from the UE, or recently allowed network slices, or a combination; store information associated with the recently allowed network slices and identifier; identify an active PDU session based at least in part on the status of the existing active PDU sessions of the configuration message, where the active PDU session is not supported by the recently allowed network slices; and locally release the active PDU session.
[0017] Another device for wireless communication is described. The apparatus may include a means for receiving, from a source AMF, a configuration message comprising an identifier associated with a target AMF, a
Petition 870190114669, of 11/08/2019, p. 12/172
8/117 situation of existing active PDU sessions of the UE, or recently allowed network slices, or a combination; means for storing information associated with recently allowed network slices and identifier; means to identify an active PDU session based at least in part on the status of the existing active PDU sessions of the configuration message, the active PDU session is not supported by the recently allowed network slices; and a half to locally release the active PDU session.
[0018] Another device for wireless communication is described. The device may include a processor, memory in electronic communication with the processor. The processor and memory can be configured to receive, from a source AMF, a configuration message comprising an identifier associated with a target AMF, a status of existing active PDU sessions from the UE, or recently allowed network slices, or a combination; store information associated with the recently allowed network slices and identifier; identify an active PDU session based at least in part on the status of the existing active PDU sessions of the configuration message, the active PDU session is not supported by the recently allowed network slices; and locally release the active PDU session.
[0019] Another non-transitory, computer-readable means for wireless communication is described. The non-transitory computer-readable medium may include operable instructions to have a processor receive, from a source AMF, a configuration message comprising an identifier associated with a target AMF, a
Petition 870190114669, of 11/08/2019, p. 13/172
9/117 situation of existing active PDU sessions of the UE, or recently allowed network slices, or a combination; store information associated with the recently allowed network slices and identifier; identify an active PDU session based at least in part on the status of the existing active PDU sessions of the configuration message, the active PDU session is not supported by the recently allowed network slices; and locally release the active PDU session.
[0020] In some examples of the non-transitory computer-readable method, apparatus and medium described above, the identifier comprises a GUTI of NR.
[0021] Another method for wireless communication in an AMF-source is described. The method may include determining to modify currently allowed network slices used by a UE based at least in part on a received network trigger; identify recently allowed network slices for the UE based at least in part on the determination; and determining that a target AMF associated with the recently allowed network slices is inaccessible by the source AMF.
[0022] Another device for wireless communication is described. The apparatus may include means for determining that currently permitted network slices used by a UE are modified based at least in part on a received network trigger; means for identifying recently allowed network slices for the UE based at least in part on the determination; and means for determining that a target AMF associated with the recently allowed network slices is inaccessible by the source AMF.
Petition 870190114669, of 11/08/2019, p. 14/172
11/10
[0023] Another device for wireless communication is described. The device may include a processor, memory in electronic communication with the processor. The processor and memory can be configured to determine that the currently allowed network slices used by a UE are modified based at least in part on a received network trigger; identify recently allowed network slices for the UE based at least in part on the determination; and determine that a target MFA associated with the recently allowed network slices is inaccessible by the device.
[0024] Another non-transitory, computer-readable means for wireless communication is described. The non-transitory computer-readable medium may include operable instructions to have a processor determine that the currently allowed network slices used by a UE are modified based at least in part on a received network trigger; identify the network slices recently allowed for the UE based at least in part on the determination; and determining that a target MFA associated with the recently allowed network slices is inaccessible by a source MFA.
[0025] Some examples of the non-transitory computer-readable method, apparatus and medium described may additionally include processes, resources, means or instructions for transmitting a deregistration request to the UE based at least in part on the determination that the MFA target is inaccessible by AMFfonte. In some examples of the non-transitory computer-readable method, apparatus and medium described above, the
Petition 870190114669, of 11/08/2019, p. 15/172
11/117 deregistration request comprises an indication to perform a re-registration procedure, recently allowed network slices, or a code indicating that the deregistration request is in response to a change in supported network slices, or a combination. Some examples of the non-transitory computer-readable method, apparatus, and medium described may additionally include processes, resources, means, or instructions for triggering a procedure for releasing an active PDU session associated with currently permitted network slices that are not supported by the slices of recently allowed network; and release the UE context comprising an active PDU session progress report or an NR GUTI, or both based at least in part on the trigger.
[0026] Another method for wireless communication in an UE is described. The method may include identifying a request for re-registration and a code indicating a request to register a set of network slices associated with a recently allowed network slice based at least in part on a deregistration request received from an MFA -source that is serving the UE; identify recently allowed network slices based at least in part on the deregistration request received; and generate a request to register the set of network slices based at least in part on the code.
[0027] Another device for wireless communication is described. The device may include means to identify a request for new registration and a code
Petition 870190114669, of 11/08/2019, p. 16/172
12/117 indicating a request to register a set of network slices associated with a recently allowed network slice based at least in part on a deregistration request received from a source AMF serving the UE; means of identifying recently allowed network slices based at least in part on the deregistration request received; and generate a request to register the set of network slices based at least in part on the code.
[0028] Another device for wireless communication is described. The device may include a processor, memory in electronic communication with the processor. The processor and memory can be configured to identify a new registration request and a code that indicates a request to register a set of network slices associated with a recently allowed network slice based at least in part on a cancellation request. registration received from a source MFA serving the UE; identify recently allowed network slices based at least in part on the deregistration request received; and generate a request to register the set of network slices based at least in part on the code.
[0029] A non-transitory, computer-readable medium for wireless communication is described. The non-transitory computer-readable medium may include operable instructions to have a processor identify a request for new registration and a code that indicates a request to register a set of network slices associated with a newly slice of network
Petition 870190114669, of 11/08/2019, p. 17/172
11/13 permitted based at least in part on a deregistration request received from a source AMF serving the UE; identify recently allowed network slices based at least in part on the deregistration request received; and generate a request to register the set of network slices based at least in part on the code.
[0030] Some examples of the non-transitory computer-readable method, apparatus and medium described may additionally include processes, resources, means or instructions for storing information associated with recently allowed network slices, where the information comprises NSSAI. Some examples of the non-transitory computer-readable method, apparatus and medium described may additionally include processes, resources, means or instructions for removing a current NR GUTI based at least in part on the code.
[0031] In some examples of the non-transitory computer-readable method, apparatus and medium described above, an upper layer of the UE transmits to a lower layer of the UE: an indication to release a connection to a RAN and to reestablish the connection, or a NSSAI request, or an indication to refrain from providing an NR GUTI, or a combination. In some examples of the non-transitory computer-readable method, apparatus and medium described above, the upper layer comprises a layer without access layer (NAS) and the lower layer comprises an AS layer.
[0032] Some examples of the non-transitory computer-readable method, apparatus and medium described can
Petition 870190114669, of 11/08/2019, p. 18/172
14/117 additionally include processes, resources, means or instructions for transmitting a request to reestablish the connection based at least in part on the indication to reestablish the connection, where the request comprises the NSSAI request. In some examples of the non-transitory computer-readable method, apparatus and medium described above, the connection comprises a radio resource control (RRC) connection. In some examples of the non-transitory computer-readable method, apparatus and medium described above, the RRC connection release procedure or RRC connection establishment procedure based at least in part on the indication to release a connection with a RAN and to reestablish the connection.
[0033] In some examples of the non-transitory computer-readable method, device and medium described above, the connection comprises an Internet Protocol (IP) security tunnel (IPsec) connection. In some examples of the non-transitory computer-readable method, apparatus and medium described above, an IPsec tunnel release procedure or an IPsec tunnel establishment procedure based at least in part on the indication to release a connection to an RAN and to reestablish the connection.
[0034] Some examples of the non-transitory computer-readable method, apparatus and medium described may additionally include processes, resources, means or instructions for transmitting a new RRC reconfiguration request message comprising the NSSAI request, or a code indicating the path configuration
Petition 870190114669, of 11/08/2019, p. 19/172
15/117 signaling, or a current NR GUTI, or combination. Some examples of the non-transitory computer-readable method, apparatus and medium described may additionally include processes, resources, means or instructions for transmitting an Nwu message comprising the NSSAI request, or a code indicating the signaling path configuration, or a current NR GUTI, or combination. In some examples of the non-transitory computer-readable method, apparatus and medium described above, the Nwu message comprises an IKEV2 INFORMATION message, or a reconfiguration signal connection message, or both.
[0035] Another method for wireless communication with an access network (AN) is described. The method may include receiving, from an UE, an RRC connection request comprising NSSAI; identify a source MFA associated with the currently allowed network slices of the UE based at least in part on the NSSAI; determine that the NSSAI be modified based at least in part on a trigger indication; identify recently allowed network slices supported for the UE based at least in part on the determination; select a target MFA to serve the UE based at least in part on the recently allowed network slices; and trigger an AMF relocation based at least in part on the selection, where the AMF relocation comprises signaling the source AMF to redirect the RRC connection request to the target AMF.
[0036] Another device for wireless communication is described. The apparatus may include means for receiving,
Petition 870190114669, of 11/08/2019, p. 20/172
16/117 of a UE, an RRC connection request comprising NSSAI; means to identify a source MFA associated with the currently allowed network slices of the UE based at least in part on the NSSAI; means of determining whether to modify the NSSAI based at least in part on a trigger indication; identify recently allowed network slices supported for the UE based at least in part on the determination; means for selecting a target MFA to serve the UE based at least in part on the recently allowed network slices; and means for triggering an MFA relocation based at least in part on the selection, where the MFA relocation comprises signaling the source MFA to redirect the RRC connection request to the target MFA.
[0037] Another device for wireless communication is described. The device may include a processor, memory in electronic communication with the processor. The processor and memory can be configured to receive, from a UE, an RRC connection request comprising NSSAI; identify a source MFA associated with the currently allowed network slices of the UE based at least in part on the NSSAI; determine that the NSSAI be modified based at least in part on a trigger indication; identify recently allowed network slices supported for the UE based at least in part on the determination; select a target MFA to serve the UE based at least in part on the recently allowed network slices; and trigger an MFA relocation based at least in part on selection, where the MFA relocation comprises signaling the source MFA to
Petition 870190114669, of 11/08/2019, p. 21/172
11/177 redirect the RRC connection request to AMFalvo.
[0038] Another non-transitory, computer-readable means for wireless communication is described. The non-transitory computer-readable medium may include operable instructions to cause a processor to receive an RRC connection request from an UE comprising NSSAI; identify a source MFA associated with the currently allowed network slices of the UE based at least in part on the NSSAI; determine that the NSSAI be modified based at least in part on a trigger indication; identify recently allowed network slices supported for the UE based at least in part on the determination; select a target MFA to serve the UE based at least in part on the recently allowed network slices; and trigger an AMF relocation based at least in part on the selection, where the AMF relocation comprises signaling the source AMF to redirect the RRC connection request to AMFalvo.
[0039] Another method for wireless communication is described. The method may include receiving, from a UE, a request for the relocation of a source AMF associated with the currently allowed network slices of the UE based at least in part on the network slice assistance information; determine that the NSSAI be modified based at least in part on a trigger indication; identify the recently allowed network slices supported for the UE based at least in part on the determination; select a target MFA to serve the UE with
Petition 870190114669, of 11/08/2019, p. 22/172
18/117 base at least in part on recently allowed network slices; and trigger an MFA relocation based at least in part on selection, where the MFA relocation comprises initiating a redirect from the AMF UE source to the target AMF.
[0040] Another device for wireless communication is described. The apparatus may include means for receiving, from a UE, a request for the relocation of an AMF source associated with the currently allowed network slices of the UE based at least in part on the network slice assistance information; means of determining whether to modify the NSSAI based at least in part on a trigger indication; means for identifying the recently allowed network slices supported for the UE based at least in part on the determination; means for selecting a target MFA to serve the UE based at least in part on the recently allowed network slices; and means for triggering an MFA relocation based at least in part on selection, where the MFA relocation comprises initiating a redirect from the AMF UE source to the target AMF.
[0041] Another device for wireless communication is described. The device may include a processor, memory in electronic communication with the processor. The processor and memory can be configured to receive, from a UE, a request for the relocation of a source AMF associated with the currently allowed network slices of the UE based at least in part on the network slice assistance information; determine that the NSSAI be modified based at least in part on a
Petition 870190114669, of 11/08/2019, p. 23/172
19/117 trigger indication; identify the recently allowed network slices supported for the UE based at least in part on the determination; select a target MFA to serve the UE based at least in part on the recently allowed network slices; and triggering an MFA relocation based at least in part on selection, where the MFA relocation comprises initiating a redirection of the UE from the source AMF to the target AMF.
[0042] Another non-transitory, computer-readable means for wireless communication is described. The non-transitory computer-readable medium may include operable instructions to have a processor receive, from a UE, a request for the relocation of a source AMF associated with the currently allowed network slices of the UE based at least in part on the information network slice assistance; determine that the NSSAI be modified based at least in part on a trigger indication; identify the recently allowed network slices supported for the UE based at least in part on the determination; select a target MFA to serve the UE based at least in part on the recently allowed network slices; and trigger an MFA relocation based at least in part on selection, where the MFA relocation comprises initiating a redirection of the UE from the source AMF to the target AMF.
[0043] Some examples of the non-transitory computer-readable method, apparatus and medium described may additionally include processes, resources, means or instructions for transmitting an indication comprising information for the selection of the target AMF to redirect the
Petition 870190114669, of 11/08/2019, p. 24/172
11/20 RRC connection request; and transmit instructions to perform the redirection through the source AMF.
[0044] Some examples of the non-transitory computer-readable method, apparatus and medium described may additionally include processes, resources, means or instructions for establishing an N2 signaling connection with the target AMF; and transmitting a NAS message received from the UE to the target AMF using the N2 signaling connection.
[0045] Some examples of the non-transitory computer-readable method, apparatus and medium described may additionally include processes, resources, means or instructions for transmitting, to a previous UE AMF server, a request to release an N2 signaling connection. Some examples of the non-transitory computer-readable method, apparatus and medium described may additionally include processes, resources, means or instructions for receiving, from the target AMF, an updated NR GUTI for the UE; and replace a previous NR GUTI with the updated NR GUTI received for the UE.
[0046] Some examples of the non-transitory computer-readable method, apparatus and medium described may additionally include processes, resources, means or instructions for receiving, from a target AMF, an updated NR GUTI for the UE; and replace the previous NR GUTI with the updated NR GUTI received for the UE. Some examples of the non-transitory computer-readable method, apparatus and medium described may additionally include processes, resources, means or instructions for transmitting a configuration request message to the UE that
Petition 870190114669, of 11/08/2019, p. 25/172
21/117 contains the updated NR GUTI, a situation of existing active PDU sessions from the UE, indication of modification to the NSSAI, or a combination.
BRIEF DESCRIPTION OF THE DRAWINGS
[0047] Figures 1 and 2 illustrate examples of a wireless communications system that supports the enabling of changing a network slice network trigger, according to one or more aspects of the present disclosure.
[0048] Figures 3 and 4 illustrate examples of a process flow that supports the enabling of changing a network trigger of network slices, according to one or more aspects of the present disclosure.
[0049] Figures 5 to 7 show block diagrams of a device that supports the enabling of a network trigger change of network slices, according to one or more aspects of the present disclosure.
[0050] Figure 8 illustrates a block diagram of a system that includes a network entity that supports the enabling of a network trigger change of network slices, according to one or more aspects of the present disclosure.
[0051] Figures 9 to 11 show block diagrams of a device that supports the enabling of a network slicer trigger change, according to one or more aspects of the present disclosure.
[0052] Figure 12 illustrates a block diagram of a system that includes a UE that supports the enabling of a network slice switch trigger, according to one or more aspects of this
Petition 870190114669, of 11/08/2019, p. 26/172
11/22 revelation.
[0053] Figures 13 to 20 illustrate methods for enabling a network trigger change of network slices, according to one or more aspects of the present disclosure.
DETAILED DESCRIPTION
[0054] The features described refer, in general, to methods, systems and devices for wireless communication that support the enabling of a network trigger change of network slices. A UE can establish a protocol data unit (PDU) session for a logical data network. The logical data network can also be referred to as a network slice. In some cases, a UE may select a network slice based on a subscription service or application. For example, an UE may have an application that is an Internet Protocol (IP) multimedia systems (FMS) voice application, the UE may select a network slice that is configured to support that mobile broadband application. An UE may, additionally or alternatively, have an application that is configured as an Internet of Things (loT) application; for example, the loT application can configure the UE to operate as a loT communication port device that periodically compiles and transmits data to a remote server. In this way, the UE can select a network slice that is configured to support massive loT data traffic. Having different slices of network serving different applications and subscriptions, etc. the UE can improve its resource utilization on a network, while also meeting the performance requirements of
Petition 870190114669, of 11/08/2019, p. 27/172
23/117 individual applications of the UE.
[0055] UE network slices can be served by a mobility and access management (AMF) function. In addition, session management of the network slices can be performed by a session management function (SMF). The network can determine a change in a set of allowed network slices for a UE. This change can be identified; for example, comparing previously allowed network slices to recently allowed network slices. The previously allowed network slices may include a set of allowed network slices for a UE, before the network determines a change in the set of allowed network slices. In addition, recently allowed network slices may include a set of allowed network slices for the UE, after the network determines a change in the set of allowed network slices. The network may, in some cases, provide network slice selection assistance information (NSSAI) or a set of permitted NSSAIs (S-NSSAI) to the UE. NSSAIs can include information indicating network slices allowed or supported for the UE to use, within other information.
[0056] The network can change a set of network slices for a UE. For example, in the case where a new network slice is identified in the set of recently allowed network slices, a current MFA serving the UE may determine a lack of capacity to service the new network slice. As a result, an MFA that can serve the new network slice can be identified. In others
Petition 870190114669, of 11/08/2019, p. 28/172
24/117 words, a change to a set of allowed network slices may involve a change to a server AMF. In one respect, a current MFA can reach a new MFA. The new MFA may not serve isolated network slices. In another aspect, the recently allowed network slices can be isolated. In other words, the current AMF serving the recently allowed network slices can purchase a new AMF that is not accessible by other AMFs. In some instances, the network may change a set of network slices that the UE is using, while the UE is in an RM REGISTERED state.
[0057] The state REGISTERED BY RM, the UE can now be registered with an AMF for one or more network slices. The UE may refer to one or more network slices in an initial NSSAI application during an initial registration procedure with the MFA. In case the network changes the set of network slices, the network can transmit a new NSSAI to the UE. The UE can receive the new NSSAI. The UE can re-register with a requested NSSAI including the current S-NSSAI with which the UE is registered and a new SNSSAI. Due to the new NSSAI requested, if the network determines that a different AMF (that is, not the current AMF) is required to serve the UE, the network can identify and select a new AMF.
[0058] In some cases, the UE performs a new registration procedure. The network may not allow a direct transfer between a serving AMF and a new target AMF due to the fact that the new AMF is associated with a different registration area or is isolated. In that case, session and service continuity may not be considered,
Petition 870190114669, of 11/08/2019, p. 29/172
25/117 where the new registration procedure is appropriate. However, existing re-registration procedures may not provide enough information for the UE to act accordingly. Alternatively, a network can use the UE configuration update procedure to update a set of NSSAIs that the UE is allowed to use, by providing a new set of NSSAIs in the UE configuration update request message. However, in some cases, the UE may not need to register again due to the NSSAI change (for example, a new network slice may be available and the UE requires connectivity to do so, or the applications that were using a slice of may no longer be available in the PDU sessions of another network slice to which the UE is not registered). As a result, the UE may acknowledge the NSSAI update allowed with a UE configuration update completion message. If the UE requires additional S-NSSAI in addition to the values received (for example, S-NSSAI in the configured NSSAI that was not previously requested), then the UE can initiate a registration procedure. The network can then confirm with the registration acceptance message. However, simple UE notification may not be sufficient in terms of using temporary ID (eg 5G GUTI) and NSSAI requests.
[0059] Thus, existing solutions do not support the relocation of a serving AMF to a UE when the current AMF can reach a target AMF (that is, the target AMF does not serve isolated slices) or when the network slices recently allowed are isolated (that is, MFA
Petition 870190114669, of 11/08/2019, p. 30/172
26/117 serving the new network slice (or slices) requires a separate AMF not reachable by other AMFs). The present disclosure provides techniques for relocating MFA based on network trigger changes from network slices. According to one technique, a current MFA can identify a request to change an NSSAI currently allowed for an UE. The current AMF may identify a request to modify the NSSAI currently permitted based on a policy control function (PCF) indication or an indication that designates a change to a subscription to a network slice. In some instances, the request may include a recently permitted NSSAI.
[0060] The current MFA can select a new MFA based on the NSSAI recently allowed. If a new AMF can be selected and obtained by the current AMF, the current AMF can determine whether the UE has an active NSI of S-NSSAI associated with the recently permitted NSSAIs or an active NSI that is absent in the recently permitted NSSAI, or both. The current MFA can generate an EU context and can convey the EU context to the new MFA. The UE context can include an EU PDU situation for all existing EU PDU sessions for each active network slice, associated with the recently allowed NSSAI. Thus, the network trigger change results in the current AMF which triggers the relocation of AMF (that is, a change from a current AMF to a new AMF).
[0061] The current AMF can transmit an AMF relocation request to a new AMF. The AMF relocation request may include an NSSAI
Petition 870190114669, of 11/08/2019, p. 31/172
27/117 recently allowed or EU context, or both. In addition, the current AMF may trigger a PDU release procedure for each active UE PDU session that is not supported in the recently allowed NSSAI. The new AMF can receive the relocation request from the current AMF (that is, the previous AMF, now). Based on the relocation request, the new AMF can transmit an indication, to one or more SMFs associated with an active UE PDU session, that identifies the change to the AMF. In some instances, the UE may have a plurality of active UE PDU sessions. The new AMF can determine and allocate an NR GUTI (for example, or another 5G network identifier) to the UE. The UE can receive the new AMF NR GUTI in a message; for example, in a UE configuration request message. The message may also include a situation provided by the previous AMF or the recently permitted NSSAI, or both. The situation may indicate UE PDU sessions for each active network slice. In some instances, the situation may indicate a plurality of UE PDU sessions for a plurality of active network slices. Upon receipt of the new AMF message, the UE can store the newly allowed NSSAI, the new NR GUTI, and can release the active UE PDU sessions that are absent in the UE PDU session situation.
[0062] In some cases, the UE may determine that an additional network slice is required in addition to the network slices included in the recently allowed NSSAI that were missing from the previous permitted NSSAI. The UE can register again with the network based on the determination of
Petition 870190114669, of 11/08/2019, p. 32/172
28/117 that additional network slices are required. For example, in the previous permitted NSSAI, the UE can be assigned network slices 0-3; however, in the recently allowed NSSAI, the UE may have assigned network slices 1, 2, and 4. In this way, the UE may determine that the network slice 4 needs to be registered. As part of the new registration with the network, the UE can transmit an NSSAI request. The NSSAI request may include the additional network slice in addition to the currently registered network slices.
[0063] According to a second technique, a new registration procedure can be triggered by the network. In this case, the current AMF may identify a request to change one or more network slices associated with an NSSAI currently allowed. In response to request identification, the current AMF may select a new AMF to serve the network slices associated with the recently permitted NSSAI. However, the current AMF may determine that the new AMF is not accessible. As a result, the current AMF may transmit a deregistration request to the UE. The deregistration request may include an indication to perform a re-registration procedure. In addition, the deregistration request may include the newly permitted NSSAI or a cause code that indicates a new registration request for a set of network slices due to an AMF change, or both.
[0064] In some cases, the current AMF may refrain from releasing an N2 signaling connection, until a request to release the connection is received from the network (for example, RAN). In the case that the current MFA receives the
Petition 870190114669, of 11/08/2019, p. 33/172
29/117 network request, the current MFA can trigger a PDU release procedure. This procedure may include that for each active UE PDU session that is not supported in the recently allowed NSSAI, the UE PDU session is released. When all EU PDU sessions are released, the MFA can also release the EU context.
[0065] The UE may receive the cancellation request from the current AMF. In some cases, the UE may determine that the deregistration request includes a re-registration request; for example, the new registration request can be identified in a cause code that indicates a new registration request for a new network slice based on an AMF change. The UE can determine a permitted NSSAI based on the deregistration request, and store the permitted NSSAI locally or remotely, or both. In some cases, the UE may determine which network slices in the NSSAI recently allowed to connect in order to create an NSSAI request.
[0066] Additionally or alternatively, the UE can analyze the cause code to perform additional operations. The UE can, for example, remove a current GUTI (for example, 5G GUTI) based on the cause code. In some cases, an upper layer (for example, NAS layer) of the UE may indicate to a lower layer (for example, AS layer) that either release a signaling connection or reestablish a signaling connection to the network, or both with based on the cause code. The UE can transmit a
Petition 870190114669, of 11/08/2019, p. 34/172
11/307 request to reestablish a signaling connection including the NSSAI request, to the network.
[0067] In some examples, the signaling connection may be an RRC connection. In this case, the UE can perform an RRC connection release or an RRC connection establishment procedure, or both. The network can receive the signaling indication associated with the RRC connection release or the RRC connection establishment procedure. The signaling indication may include an NSSAI request. The NSSAI request may contain an indication of network slices requested based on the NSSAI. According to one technique, the network can determine a change in the NSSAI for a UE. The network can modify the NSSAI currently allowed based on a PCF indication or an indication designates a change to a subscription to a network slice. In some examples, the modification may include identifying the recently allowed network slices supported for the UE, either alone or added to the NSSAI request network slices. The network can select a new AMF to serve the network slices associated with the newly permitted NSSAI and initiate an AMF relocation for the signaling connection of the RRC connection release or RRC connection establishment. In other words, a change to a set of allowed network slices may involve a change to a server AMF for RRC connectivity. In one respect, a current MFA can reach a new MFA. Communication between the current AMF and the new AMF can be redirected through the network or established through a direct connection between the AMFs.
Petition 870190114669, of 11/08/2019, p. 35/172
11/31
Alternatively, the signaling connection can be an Nwu connection; for example, an IPSec tunnel connection. In that case, the EU can release or reestablish the IPSec tunnel connection, or both.
[0068] In some cases, an upper layer (for example, NAS layer) of the UE may indicate to a lower layer (for example, AS layer) that modifies a signaling connection to the network based on the cause code. In this case, the UE can transmit a message (for example, a new RRC reconfiguration request message or Nwu signaling) for the network to modify a signaling connection. In some cases, the reconfiguration message reconfiguration message or Nwu signaling may include the NSSAI request, or a signaling path reconfiguration indicated by the cause code, or a current GUTI (for example, 5G GUTI), or a combination of them for the network. In addition, the UE may include a NAS message that includes the NSSAI request in the RRC reconfiguration message. In some cases, the message transmitted to the network by the UE may be an IKEV2 INFORMATION message. This message can be identified by an exchange-type value set to a predetermined number (for example, 37), or a new connection message by reconfiguration signaling identified by an exchange-type value defined between a predetermined range (for example, a between 240 and 255) that can be reserved for private use. In some examples, the NSSAI request, the cause code that indicates a signal path reconfiguration, or the GUTI, or a combination of them can be included in a
Petition 870190114669, of 11/08/2019, p. 36/172
32/117 generic payload with a payload type set to a predetermined number (for example, 43) to indicate a supplier ID payload.
[0069] The network can receive the RRC reconfiguration request message from the UE. At that point, the network can select a server AMF based on the NSSAI request included in the RRC reset request message. According to one technique, the network can evaluate the considerations of the currently allowed network slices associated with the NSSAI request. In some cases, the network may determine a change in the NSSAI for the UE. The network can modify the NSSAI currently allowed based on a PCF indication or an indication designates a change to a subscription to a network slice. In some examples, the modification may include identifying the recently allowed network slices supported for the UE, either alone or added to the NSSAI request network slices. The network can select a new MFA to serve the network slices associated with the newly permitted NSSAI and initiate an MFA relocation. In other words, a change to a set of allowed network slices may involve a change to a server AMF. In one respect, a current MFA can reach a new MFA. The network can establish an N2 signaling connection with the serving AMF and transmit the NAS message received from the UE. Additionally or alternatively, the network may transmit a request, to release an N2 signaling connection, to a previous AMF. Once the network registers with the AMF server, the network can receive a new AMF server
Petition 870190114669, of 11/08/2019, p. 37/172
11/33
GUTI for the UE. As a result, the network can transmit the new GUTI to the UE. In some instances, the network may transmit the same message as the UE. For example, the network can transmit the new GUTI in a generic payload with a payload type associated with a supplier ID payload.
[0070] The aspects of the disclosure are initially described in the context of a wireless communications system. UEs, base stations (for example, eNB, gNB), exemplary systems and process flow for MFA relocation based on network trigger changes from network slices are then described. The aspects of the disclosure are further illustrated and described with reference to the device diagrams, system diagrams and flowcharts that refer to enabling a network trigger change of network slices.
[0071] Figure 1 illustrates an example of a wireless communications system 100 that supports the enabling of changing a network slice network trigger, in accordance with one or more aspects of the present disclosure. The wireless communications system 100 includes base stations 105 (for example, gNodeBs (gNBs), and / or radio heads (RHs)), UEs 115 and a main network 130. In some examples, the wireless communications system 100 can be a Long Term Evolution (LTE), Advanced LTE (LTE-A) network or an NR network. In some cases, the wireless communications system 100 can support enhanced broadband communications, ultra-reliable communications (ie, mission critical),
Petition 870190114669, of 11/08/2019, p. 38/172
34/117 low latency, and communications with low cost and low complexity devices.
[0072] The UE 115 can establish multiple PDU sessions for multiple network slices. In some cases, the UE 115 may select a network slice based on a subscription service or application. Having different slices of network serving different applications or subscriptions, etc. the UE 115 can enhance its resource utilization in wireless communications system 100, while also supporting the performance requirements of individual UE 115 applications. In some cases, the network slices used by the UE 115 can be served by an associated MFA base station 105 or main network 130, or both. In addition, session management of network slices can be performed by an SMF.
[0073] In some cases, a network (for example, RAN) can determine a change in a set of allowed network slices for a UE 115. That change can be determined; for example, comparing previously allowed network slices to recently allowed network slices. An AMF may, in some cases, provide NSSAI or an S-NSSAI to the UE 115. NSSAIs may include information that indicates allowed network slices for the UE 115 to use, among other information. The AMF may, in some cases, change a set of network slices to the UE 115. For example, in the case where a new network slice is identified in the set of recently allowed network slices, an AMF serving the EU 115 may determine that the AMF server does not have the capacity to serve the new network slice. As a result, an MFA that can serve the new
Petition 870190114669, of 11/08/2019, p. 39/172
35/117 network slice can be identified. In other words, a change to a set of allowed network slices may involve a change to a server AMF.
[0074] In case a network changes the set of network slices, a server AMF can transmit a new set of NSSAIs to the UE 115. The UE 115 can receive the new set of NSSAIs. In some cases, the UE 115 may identify that the new set of NSSAIs includes new S-NSSAIs to which the UE 115 may need to connect. UE 115 can re-register with a requested NSSAI that includes the current S-NSSAIs with which UE 115 is registered and one or more of the new S-NSSAIs. Depending on the new NSSAI requested, if the serving AMF determines that a different AMF is required for the UE 115, the serving AMF can identify and select a new AMF. As a result, the wireless communications system 100 is able to withstand changes triggered by the network for the network slices.
[0075] Base stations 105 can communicate wirelessly with UEs 115 through one or more base station antennas. Each base station 105 can provide communication coverage for a respective geographic coverage area 110. The communication links 125 shown on the wireless communication system 100 can include uplink (UL) transmissions from an UE 15 to a station -based 105 or downlink (DL) transmissions, from a base station 105 to a UE 115. Control information and data can be multiplexed on an uplink channel or downlink channel according to various techniques. At
Petition 870190114669, of 11/08/2019, p. 40/172
36/117 information and control data can be multiplexed on a downlink channel, for example, using time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques or TDM-FDM hybrids. In some examples, the control information transmitted during a transmission time interval (TTI) of a downlink channel can be distributed between different control regions in a cascade manner (for example, between a common control region and a or more control regions specific to the EU).
[0076] UEs 15 can be dispersed throughout the wireless communication system 100, and each UE 115 can be stationary or mobile. A UE 115 can also be referred to as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device , a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a customer or some other suitable terminology. An UE 115 can also be a cell phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a portable device, a tablet computer, a laptop computer, a cordless phone , a personal electronic device, a portable device, a personal computer, a wireless local loop station (WLL), an Internet of Things (loT) device, a loE device, a
Petition 870190114669, of 11/08/2019, p. 41/172
37/117 machine-type communication device (MTC), an instrument, an automobile, or the like.
[0077] In some cases, a UE 115 may also be able to communicate directly with other UEs (for example, using a peer-to-peer (P2P) or device to device (D2D) protocol). One or more of a group of UEs 115 using D2D communications may be within the geographic coverage area 110 of a cell. Other UEs 115 in such a group may be outside a cell's geographic coverage area 110 of a cell or otherwise unable to receive transmissions from a base station 105. In some cases, groups of UEs 115 communicating via D2D communications can use a one to many (1: M) system in which each UE 115 transmits to each other UE 115 in the group. In some cases, a base station 105 makes it easy to program resources for D2D communications. In other cases, D2D communications are carried out independently of a base station 105.
[0078] Some UEs 115, such as MTC or ToT devices, can be low cost or low complexity devices, and can provide automated communication between machines, that is, Machine to Machine (M2M) communication. M2M or MTC can refer to data communication technologies that allow devices to communicate with each other or with a base station without human intervention. For example, M2M or MTC can refer to the communications of devices that integrate sensors or meters to measure or capture information and rely on the information for a central server or application program that can make use of the information or present
Petition 870190114669, of 11/08/2019, p. 42/172
38/117 the information for humans that interact with the program or the application. Some UEs 115 can be designed to collect information or enable automated machine behavior. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, health service monitoring, wildlife monitoring, geological and climate event monitoring, fleet management and tracking, remote security detection, physical access control, and transaction-based business loading.
[0079] The base stations 105 can communicate with the main network 130 and with another one. For example, base stations 105 can interface with main network 130 through backhaul links 132 (e.g., SI, etc.). Base stations 105 can communicate with each other via backhaul links 134 (for example, X2, etc.) either directly or indirectly (for example, through main network 130). An UE 115 can communicate with the main network 130 via communication link 135. Base stations 105 can perform radio and programming configuration for communication with UEs 115, or can operate under the control of a base station controller (not shown). In some examples, base stations 105 may be macrocells, small cells, access points, or the like. Base stations 105 can also be referred to as evolved NodeBs (eNBs) 105.
[0080] A base station 105 can be connected via an SI interface to the main network 130. The main network can be an evolved packet core (EPC), which
Petition 870190114669, of 11/08/2019, p. 43/172
39/117 can include at least one mobility management entity (MME), at least one server communication port (S-GW), and at least one Packet Data Network (PDN) Communication Port (P-GW) ). The MME can be the control node that processes the signaling between the UE 115 and the EPC. All user IP packets can be transferred via S-GW, which can itself be connected to P-GW. P-GW can provide IP address allocation as well as other functions. The P-GW can be connected to the IP services of network operators. Operator IP services may include the Internet, an Intranet, an IP Multimedia Subsystem (IMS) and / or a Packet Switched (PS) Streaming Service.
[0081] Main network 130 can provide user authentication, access authorization, tracking, IP connectivity, and other access, routing or mobility functions. At least some of the base stations 105 (for example, eNodeBs (eNBs, network access devices, gNBs) 105-a, gNBs, or access node controllers (ANCs) can interface with the main network 130 via links backhaul 132 (eg SI, S2, etc.) and can carry out radio configuration and programming for communication with UEs 115. In some configurations, various functions of each access network entity or base station 105 can be distributed through multiple network devices (for example, radio heads and access network controllers) or consolidated into a single network device (for example, a 105 base station).
[0082] One or more of the network devices 105
Petition 870190114669, of 11/08/2019, p. 44/172
40/117 may include a network slice manager 101, which can receive a network trigger; determine to modify the currently permitted network slice associated with a currently permitted NSSAI used by the UE 115 based on the received network trigger; identify NSSAI recently allowed for UE 115 based on determination; and selecting a target AMF based on the recently permitted NSSAI, where the target AMF is accessible by the source AMF. The network slice manager 101 may alternatively receive an AMF relocation request for the UE 115 currently served by a source AMF, the AMF relocation request may include a recently permitted NSSAI and UE context information. Network slice manager 101 can allocate an updated NR GUTI to UE 115 based on the AMF relocation request; and transmitting to the UE 115 a configuration request message that includes the updated NR GUTI, an updated status of an existing UE PDU session, or the recently allowed NSSAI, or a combination thereof.
[0083] In some cases, the network slice manager 101 may receive a network trigger from an UE 115 served by an AMF-source; determine to modify the currently permitted NSSAI associated with a currently permitted S-NSSAI used by the UE 115 based on the received network trigger; identify the NSSAI recently allowed for UE 115; and to determine that a target AMF associated with the recently permitted NSSAI is inaccessible by the source AMF. Alternatively, in some cases, the network slice manager 101 may receive an RRC connection request from the UE 115 that includes NSSAI; select a target MFA
Petition 870190114669, of 11/08/2019, p. 45/172
41/117 to serve the UE 115 based on the NSSAI; establish an N2 signaling connection with the selected AMF; and transmitting the NAS message received from the UE 115 to the selected AMF using the N2 signaling connection.
[0084] UEs 115 may include a network slice manager 102, which may receive, from a network device 105, a configuration message indicating a request to register one or more new network slices associated with a network slice recently allowed, a NR GUTI associated with a target AMF, an existing active EU PDU session of UE 115, or recently allowed NSSAI, or a combination thereof; store the recently allowed NSSAI and NR GUTI; identify an active UE PDU session based on the status of existing active UE PDU session information included in the configuration message, the identified active UE PDU session is not supported in the recently allowed NSSAI; and release the identified active UE PDU session. Additionally or alternatively, the network slice manager 101 may identify a request for new registration and a code that indicates a request to register a set of network slices associated with a recently permitted NSSAI based on a deregistration request received from an MFA that is serving UE 115; identify the recently permitted NSSAI based on the registration cancellation request received; and generate an NSSAI request to register the set of network slices based on the code.
[0085] In some instances, the establishment
Petition 870190114669, of 11/08/2019, p. 46/172
42/117 of a user plan connection to a data network through one or more network slice instances may include performing a resource management procedure to select an AMF that supports one or more network slices. In addition or alternatively, the management procedure may include establishing a PDU session for the data network through the network slice instance. The UE 115 can register with a network (for example, PLMN, LTE, NR). When the UE 115 registers with the network, the UE 115 can determine a configured NSSAI or an allowed NSSAI. The UE 115 can provide the network using RRC and NAS layer with an NSSAI request based on the determination of a configured NSSAI or an allowed NSSAI. The NSSAI request can include S-NSSAI associated with the network slice to which the UE 115 requests registration. In addition, the NSSAI request may include a temporary identifier (for example, GUTI) assigned to UE 115.
[0086] The NSSAI request can include a configured NSSAI or a subset of the configured NSSAI, in the case that the UE 115 has an NSSAI not allowed or NSSAI not allowed. In some cases, the NSSAI request may include the permitted NSSAI, or a subset of the permitted NSSAI, one or more S-NSSAIs associated with the configured NSSAI for which no corresponding S-NSSAI is supported in the permitted NSSAI, and which have not been previously supported by the network. The subset of permitted NSSAI may include an S-NSSAI associated with the previous permitted NSSAI for the network, in some examples.
[0087] The UE 115 can provide, on request
Petition 870190114669, of 11/08/2019, p. 47/172
43/117 of NSSAI, a configured NSSAI S-NSSAI that the UE 115 previously supplied to the network in a current registration area. The NSSAI request can also be included in an RRC connection establishment message or the NAS message, or both. The network (for example, RAN) can route NAS signaling between the UE 115 and a selected AMF using the requested NSSAI obtained during an RRC connection establishment. If the network (for example, RAN) is unable to select an AMF based on the requested NSSAI, the network can route the NAS signaling to an AMF from a set of standard AMFs.
[0088] In some cases, upon registration, the UE 115 may be provided with a temporary identifier by a serving MFA. The temporary identifier may be included in one or more RRC connection establishment messages during subsequent initial accesses to enable the network (for example, RAN) to route NAS signaling between the UE 115 and a suitable AMF. The network can also return a recently allowed NSSAI that identifies allowed network slices. UE 115 can store the newly allowed NSSAI and replace any previously allowed NSSAI stored for the network.
[0089] The network can also discard an SNSSAI provided by UE 115 in an NSSAI requested with a discarded cause code. In some instances, the network may transmit an indication that identifies whether the discarded S-NSSAI is permanent (for example, the S-NSSAI may not be supported by the network in at least the current registration area) or temporary (for example, the network slice
Petition 870190114669, of 11/08/2019, p. 48/172
44/117 associated with the S-NSSAI may be temporarily unavailable). In some cases, when receiving an NSSAI request and a temporary identifier in an RRC message from the UE 115, if the network (for example, RAN) determines the ability to obtain an AMF associated with the temporary identifier, the network may forward the request to the MFA. Alternatively, the network can select a suitable AMF based on the NSSAI request provided by UE 115, and forward the request to the selected AMF. In some cases, if the network is unable to select an AMF based on the NSSAI request, then the request can be sent to a standard AMF.
[0090] In some cases, when the UE 115 registers with a network, if the UE does not have NSSAI configured or NSSAI allowed, the network (for example, RAN) may route some or all of the NAS signaling to and from the UE 115 for a standard AMF. The UE 115 can also transmit an NSSAI indication at an RRC connection establishment or initial NAS message; unless the UE 115 has an NSSAI configured or NSSAI allowed for a corresponding network. In some cases, upon registration, the UE 115 may receive a temporary identifier through an MFA. In addition, the UE 115 can receive an allowed NSSAI that identifies network slices allowed by the network for the UE 115. The network slices can be part of the standard inscribed S-NSSAI of the UE 115. The UE 115 can also include the temporary identifier in an RRC connection establishment message during subsequent initial accesses to enable the network to route NAS signaling between the UE 115 and a suitable MFA.
Petition 870190114669, of 11/08/2019, p. 49/172
45/117
[0091] In some examples, the wireless communications system 100 can provide modification for a network slice for the UE 115. In addition, the wireless communications system 100 can provide modification for a set of network slices for the UE 115 115. A set of network slices for the UE 115 can change during instances again and follow the record with a network. In addition, a change to the network slice set can be initiated by the network, or the UE 115 based on one or more conditions. The network can change a set of network slices for which the UE 115 is registered based on local policies; for example, subscription changes or EU mobility, or both.
[0092] In some cases, the network may trigger the change to the set of network slices during a registration procedure. For example, an access node (AN) on the network may receive an RRC connection request from the UE 115 that includes NSSAI; and determining a change in NSSAI network slice considerations currently permitted used by an AMF-source registration procedure. The AN may determine to modify the NSSAI currently permitted based on a network trigger of local policies; and identifying a recently allowed NSSAI that includes recently allowed network slices supported for the UE 115. In other cases, a network may receive a request initiated by the UE for relocating a source AMF associated with a set of currently allowed network slices from a network connection. The AN may determine a change in consideration of the NSSAI network slice currently allowed
Petition 870190114669, of 11/08/2019, p. 50/172
46/117 used by the MFA-source; and determine to modify the NSSAI currently permitted based on local network policies and the relocation request.
[0093] The network can also select a new MFA based on the NSSAI recently allowed. In some cases, the network may determine that a redirect between a current AMF and the newly selected AMF is possible. As a result, the network can trigger a relocation of AMF towards the new AMF and the current AMF can transmit the NSSAI recently allowed for the newly selected AMF. The current AMF can also trigger the release of PDU sessions for an S-NSSAI that are not supported by the recently permitted NSSAI. The current AMF can communicate with the new AMF according to redirection over the network or direct signaling between AMFs. Alternatively, the network may determine that relocation to a new MFA that supports the recently permitted NSSAI is not possible. As a result, the current AMF can transmit the newly permitted NSSAI to the UE 115 using a network-initiated re-registration procedure. The re-registration procedure may include an indication for the UE 115 to initiate a registration procedure with the new and updated S-NSSAI, and that the reason for the new registration is due to the change in the supported network slices. As a result, the UE 115 can initiate a registration procedure that includes an NSSAI request based on the recently permitted NSSAI, an abstention from providing the current temporary identifier of the UE 115.
[0094] A data network can be associated with an S-NSSAI. In some cases, a network operator may
Petition 870190114669, of 11/08/2019, p. 51/172
47/117 provide the UE 115 with the network slice selection (NSSP) policy. The NSSP can include one or more NSSP rules, each of which is associated with an application with a specific S-NSSAI. In some cases, a standard rule may be compatible with all applications to an S-NSSAI. In some cases, a UE 115 application associated with an SNSSAI may request data transmission. If the UE 115 has one or more PDU sessions established and associated with the S-NSSAI, the UE 115 may route user data for that application in one of those PDU sessions, unless other conditions in the UE 115 do not allow the use of those PDU sessions PDU sessions. In addition, if the UE 115 application provides a DNN, the UE 115 can determine which PDU session to use. In some cases, if the UE 115 does not have a PDU session established and associated with the S-NSSAI, the UE 115 may request a new PDU session associated with the S-NSSAI and with a DNN that can be provided by the application. In order for the network to select a suitable resource to support network slicing in the RAN, the RAN needs to be aware of the network slices used by the UE 115. An AMF can select an SMF in a network slice instance based on the S -NSSAI, DNN and other information; for example, UE and local operator subscription policies, when the UE triggers the establishment of a PDU session. The selected SMF establishes a PDU session based on the S-NSSAI and DNN.
[0095] The wireless communication system 100 can operate in an ultra-high frequency frequency (UHF) region that uses frequency bands from 700 MHz to 2,600 MHz (2.6 GHz), although some networks (for example , a wireless local area network (WLAN) can use frequencies as
Petition 870190114669, of 11/08/2019, p. 52/172
48/117 high as 4 GHz. This region can also be known as the decimetric band, since the wavelength range of approximately one decimeter to one meter in length. UHF waves can propagate mainly by line of sight, and can be blocked by construction and environmental resources. However, the waves can penetrate walls sufficiently to provide service to the 115 internally located UEs. UHF wave transmission is characterized by smaller antennas and shorter range (for example, less than 100 km) compared to transmission using the lower frequencies (and longer waves) of the high frequency (HE) portion or very high frequency high (VHF) of the spectrum. In some cases, the wireless communications system 100 may also use extremely high frequency (EHF) portions of the spectrum (for example, from 30 GHz to 300 GHz). This region can also be known as the millimeter band, since the wavelength range of approximately one millimeter to one centimeter in length. Thus, EHF antennas can be even smaller and more closely spaced than UHF antennas. In some cases, this may facilitate the use of antenna arrays on an UE 115 (for example, for directional beam formation). However, EHF transmissions can be subjected to even greater atmospheric attenuation and shorter range than UHF transmissions.
[0096] Thus, the wireless communication system 100 can support millimeter wave (mmW) communications between UEs 115 and base stations 105. Devices operating in mmW or EHF bands can have multiple antennas to allow beam formation . That is, a station
Petition 870190114669, of 11/08/2019, p. 53/172
49/117 base 105 can use multiple antennas or antenna arrays to conduct beamforming operations for directional communications with a UE 115. Beaming (which can also be referred to as a filtering transmission or spatial targeting) is a technique signal processing that can be used on a transmitter (for example, a base station 105) to shape and / or direct a general antenna beam towards a target receiver (for example, a UE 115). This can be achieved by combining elements in an antenna array in such a way that signals transmitted at specific angles experience constructive interference while others experience destructive interference.
[0097] Wireless multiple input and multiple output (MEMO) systems use a transmission scheme between a transmitter (for example, a base station 105) and a receiver (for example, a UE 115), where both the transmitter and the receiver are equipped with several antennas. Some portions of the wireless communications system 100 may use beamforming. For example, base station 105 may have an array of antennas with a number of rows and columns of antenna ports that base station 105 can use for beaming in its communication with UE 115. Signals can be transmitted several times in different directions (for example, each transmission can be formed by different beams). An mmW receiver (for example, a UE 115) can attempt multiple beams (for example, antenna subarrays) while receiving the synchronization signals.
[0098] In some cases, the antennas of a
Petition 870190114669, of 11/08/2019, p. 54/172
50/117 base station 105 or UE 115 can be located within one or more antenna arrays, which can support beam formation or MIMO operation. One or more base station antennas or antenna arrays can be placed in an antenna mount, such as an antenna tower. In some cases, the antennas or antenna arrays associated with a base station 105 may be located in several geographic locations. A base station 105 can use multiple antennas or use antenna arrays to conduct beamforming operations for directional communications with an UE 115.
[0099] In some cases, the wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack. At the user level, communications at the carrier or Packet Convergence Protocol (PDCP) layer can be based on IP. A Radio Link Control (RLC) layer can, in some cases, perform packet segmentation and reassembly to communicate through logical channels. A Medium Access Control (MAC) layer can perform priority handling and multiplexing of logical channels in transport channels. The MAC layer can also use Hybrid ARQ (HARQ) to provide retransmission at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer can provide for establishing, configuring and maintaining an RRC connection between a UE 115 and a network device 105-c, network device 105 -b or main network 130 that supports radio bearers for plan data
Petition 870190114669, of 11/08/2019, p. 55/172
51/117 user. In the Physical Layer (PHY), transport channels can be mapped to physical channels.
[0100] Wireless communication system 100 can support multiple cell or carrier operation, a feature that can be referred to as carrier aggregation (CA) or multiple carrier operation. A carrier can also be referred to as a component carrier (CC), a layer, a channel, etc. The terms carrier, component carrier, cell and channel can be used interchangeably in this document. A UE 115 can be configured with multiple downlink CCs and one or more uplink CCs for carrier aggregation. Carrier aggregation can be used with other FDD and TDD component carriers.
[0101] In some cases, the wireless communication system 100 may use enhanced component carriers (eCCs). An eCC can be characterized by one or more features that include: wider bandwidth, shorter symbol duration, shorter TTIs and modified control channel configuration. In some cases, an eCC can be associated with a carrier aggregation configuration or a dual connectivity configuration (for example, when multiple server cells have a subideal or non-ideal backhaul link). An eCC can also be configured for use on unlicensed or shared spectrum (where more than one operator is allowed to use the spectrum). An eCC characterized by wide bandwidth can include one or more segments that can be used by UEs 115 that are unable to monitor all bandwidth
Petition 870190114669, of 11/08/2019, p. 56/172
52/117 or prefer to use a limited bandwidth (for example, to conserve power).
[0102] A shared radio spectrum band can be used in an NR shared spectrum system. For example, a shared NR spectrum can use any combination of licensed, shared and unlicensed spectra, among others. The flexibility of eCC symbol duration and subcarrier spacing can allow the use of eCC across multiple spectra. In some instances, the shared NR spectrum can increase the use of spectrum and spectrum efficiency, specifically through vertical (eg through frequency) and horizontal (eg through time) sharing of resources.
[0103] In some cases, the wireless communications system 100 can use both licensed and unlicensed frequency spectrum bands. For example, wireless communications system 100 may employ LTE License Assisted Access (LTE-LAA) or Unlicensed LTE radio access technology (LTE-U) or NR technology in an unlicensed band such as the 5Ghz Industrial, Scientific and Medical (ISM) band. When operating in unlicensed radio frequency spectrum bands, wireless devices such as base stations 105 and UEs 115 can employ listening before speaking (LBT) procedures to ensure that the channel is cleared before transmitting data . In some cases, operations on unlicensed bands may be based on a CA configuration in combination with CCs operating in
Petition 870190114669, of 11/08/2019, p. 57/172
53/117 a licensed band. Unlicensed spectrum operations may include downlink transmissions, uplink transmissions or both. Duplexing in unlicensed spectrum can be based on frequency division duplexing (FDD), time division duplexing (TDD) or a combination of both.
[0104] Figure 2 illustrates a wireless communications system 200 that supports the enabling of changing a network slice network trigger in accordance with one or more aspects of the present disclosure. In some examples, wireless communications system 200 may implement aspect of wireless communications system 100. Wireless communications system 200 may support network slicing. In some cases, access to network slicing may be based on a subscription and network deployment options; for example, some MFAs do not support all network slices requested by an UE. In addition, there may be isolated AMFs for some network slice (or slices) that do not support other network slices, and can be obtained by other AMFs that support the same network slice. The wireless communication system 200 can perform unregistration with the new registration for isolated network slices, and assign parameters to enable selection of a suitable MFA. In addition, for non-isolated network slices, an MFA relocation procedure can be triggered by a current MFA for the new MFA.
[0105] Wireless communication system 200 can include UE 215, which can be examples of UE 115, as described with reference to Figure 1. Wireless communication system 200 can also include component of
Petition 870190114669, of 11/08/2019, p. 58/172
54/117
AMF 205, AMF 210 component, RAN 220 component, and SMF 230 component. The AMF 205 component, AMF 210 component and AMF 210 component can be located locally or remotely to a base station or main network such as stations base 105 or main network 130, as described with reference to Figure 1.
[0106] UE 215 can establish a session with one or more network slices (not shown). In some examples, the session may include multiple PDU sessions associated with multiple network slices. A PDU session can be an association between the UE 215 and a data network (for example, AMF 205 component or AMF 210 component) that provides a PDU connectivity service. In some cases, the association can be an IP, an Ethernet, or unstructured type. The PDU connectivity service can be a service that exchanges PDUs between the UE 215 and a data network (for example, RAN 220 component). The communication links 260 shown in the wireless communication system 200 may include UL transmissions from the UE 215 to one or more network entities (for example, AMF 205 component, AMF 210 component, RAN 220 component, and SMF 230), or DL transmissions, from one or more of the network entities (e.g., AMF 205 component, AMF 210 component, RAN 220 component, and SMF 230 component) to UE 215.
[0107] The AMF 205 component can be a current AMF serving network slices used by the UE 215. These network slices can be associated with an NSSAI currently allowed. NSSAI may include parameters to assist in the selection of an RAN and a core network for a
Petition 870190114669, of 11/08/2019, p. 59/172
55/117 network slice instance used by UE 215. In some cases, a single NSSAI can be associated with multiple network slices. In some cases, the network may also select a RAN and a core network based on the EU 215 signature and capacity information. In addition, the NSSAI may include a session management NSSAI. The session management NSSAI can include a network slice service type or a network slice identifier (ID), or both. The type of network slice service can identify features and services supported by a network slice.
[0108] A network can trigger a change to the NSSAI currently allowed. For example, the network can change a parameter associated with a capacity of a network slice. That is, a network slice can change capabilities to serve a subscription. In some cases, due to a change in the network slice (or slices), the UE 215 may unregister with a current AMF and register with a new AMF. In other cases, due to a change in the network slice (or slices), the network may initiate the redirect of network connectivity through a server AMF.
[0109] According to a first technique, the AMF 205 component can trigger the relocation of AMF. MFA relocation may include triggering UE 215 to change to a new MFA. In some cases, the AMF 205 component may receive a recently permitted NSSAI based on a change to the currently permitted NSSAI. For example, the AMF 205 component may determine that an NSSAI currently allowed for UE 215 may need modification based on a network trigger
Petition 870190114669, of 11/08/2019, p. 60/172
56/117 that includes at least an indication of PCF or a change of signature. The AMF 205 component can determine to modify a currently allowed network slice used by the UE 215 based on the recently allowed NSSAI. In this way, the AMF 205 component can modify the currently permitted NSSAI used by the UE 215.
[0110] The AMF 205 component can select a new AMF based on the recently allowed NSSAI. For example, the AMF component 205 may select the AMF component 210 as the new AMF. In some cases, the AMF component 205 may also determine that the UE 215 has an active network slice (NSI) instance associated with an NSSAI of an currently permitted S-NSSAI. In some cases, the AMF 205 component can determine whether the UE 215 has one or more NSI active for any of the S-NSSAIs that belong to the currently permitted NSSAI, and which are not in the recently permitted NSSAI. That is, the AMF 205 component can identify that an active NSI supported on the currently permitted NSSAI associated with UE 215 is supported on the recently permitted NSSAI. The AMF 205 component can generate a progress report. In some cases, the progress report may be the EU context. The UE context can include a status of all existing UE PDU sessions associated with an active NSI. The AMF component can transmit the progress report to the AMF 210 component.
[0111] In some cases, the AMF 205 component may trigger the relocation of AMF due to a change in NSSAIs supported in the recently allowed NSSAI received. The AMF 205 component can transmit
Petition 870190114669, of 11/08/2019, p. 61/172
57/117 an AMF relocation request for the AMF 210 component via communication link 260. The AMF relocation request may include the recently allowed NSSAI and the progress report. In that case, the progress report may include the EU PDU status of all UE sessions that correspond to the SNSSAIs in the recently allowed NSSAI. In addition or alternatively, the progress report may include the current NR GUTI. The AMF 205 component can trigger a release procedure in some cases. Ο release procedure can be triggered based on direct signaling to UE 215. The release procedure can be a PDU release procedure for each active PDU session that is not supported in the recently allowed NSSAI. Similarly, the AMF 205 component can trigger the release procedure for the AMF 210 component via communication link 260.
[0112] According to a second technique, the RAN 220 component can determine a change in NSSAI to UE 215 and trigger the relocation of AMF. The RAN 22 0 component can determine a recently permitted NSSAI based on a change to the currently permitted NSSAI. For example, the RAN 220 component may determine that an NSSAI currently allowed for UE 215 may need modification based on a network trigger that includes at least a PCF indication or an indication designating a change to a subscription to a network slice. The RAN 22 0 component can determine to modify a network slice currently
Petition 870190114669, of 11/08/2019, p. 62/172
58/117 allowed used by UE 215 based on the recently allowed NSSAI. In this way, the RAN 220 component can modify the NSSAI currently allowed used by the UE 215.
[0113] The RAN 220 component can select a new AMF based on the NSSAI recently allowed. For example, the RAN 220 component can select the AMF 210 component as the new AMF. The RAN 220 component can then trigger the relocation of AMF due to a change in NSSAIs supported in the recently allowed NSSAI received. The RAN 220 component can transmit an AMF relocation request to the AMF 210 component via communication link 260. The AMF relocation request can include the recently allowed NSSAI and the progress report. In that case, the progress report may include the EU PDU status of all UE sessions that correspond to the SNSSAIs in the recently allowed NSSAI. In addition or alternatively, the progress report may include a current NR GUTI. The AMF 210 component can receive the progress report and provide a response that includes an updated NR GUTI for UE 215.
[0114] At least one of the AMF 210 component and the RAN 220 component can transmit an indication that identifies a change in AMF (for example, change from the AMF component 205 to the AMF 210 component) for associated network slices to the NSSAI recently allowed for the SMF 230 component. These network slices can be associated with an active PDU session (or sessions). In some examples, network slices can be associated with an equal or different SMF component 230.
Petition 870190114669, of 11/08/2019, p. 63/172
59/117
As a result, the AMF component 210 can transmit the indication to multiple SMF components (not shown). In some cases, the AMF 210 component may determine and allocate a GUTI NR (for example, or another 5G network identifier) to the UE 215. The UE 215 can receive the AMF 210 component's NR GUTI in a message; for example, in a UE configuration request message via 260 communication links. The message can also include an UE PDU session progress report (for example, associated with the UE context) provided by the AMF component 205 or the recently permitted NSSAI, or both.
[0115] The message may alternatively be an IKEV2 INFORMATION message. This message can be identified by an exchange-type value set to a predetermined number (for example, 37), or a new connection message by reconfiguration signaling identified by an exchange-type value defined between a predetermined range (for example, a between 240 and 255) that can be reserved for private use. In some examples, the NSSAI request, the cause code that indicates a signal path reconfiguration, or the GUTI, or a combination of them can be included in a generic payload with a payload type set to a predetermined number (e.g. 43) to indicate a vendor ID payload.
[0116] Upon receipt of the message from the AMF 210 component, the UE 215 can store the newly permitted NSSAI, the new NR GUTI and release active PDU sessions that are missing from the progress report
Petition 870190114669, of 11/08/2019, p. 64/172
60/117 EU PDU session. In some cases, the UE 215 may determine that several additional network slices are required in addition to the network slices included in the recently permitted NSSAI. In other words, the number of additional network slices may not have been supported in the previous permitted NSSAI. UE 215 can re-register with a network (for example, base station) based on the determination that additional network slices are assigned. For example, in the previous permitted NSSAI, UE 215 can be assigned network slices 1, 2 and 3; however, in the recently allowed NSSAI, the UE may have assigned network slices 1, 4 and 5. In this way, the UE can determine which network slices 4 and 5 are recently supported. As part of the new registration with the network, UE 215 can transmit an NSSAI request. The NSSAI request may include the additional network slice (or slices) (for example, network slices 4 and 5) and the currently registered network slices. In this way, the UE can determine that the network slice 4 needs to be registered. As part of the new registration with the network, the UE can transmit an NSSAI request.
[0117] In some instances, during a registration procedure on the wireless communications system 200, the RAN 220 component may determine that the UE 215 must be served by a different AMF (for example, AMF Component 210 instead of component AMF 2 05) based on network slices identified in a recently permitted NSSAI. In some cases, the AMF 205 component may receive a registration request for the RAN 220 component. In the event that the RAN component
Petition 870190114669, of 11/08/2019, p. 65/172
61/117
220 determines that aspects of the network slices identified in the recently permitted NSSAI must be served by the AMF 210 component, the RAN 220 component may trigger an AMF relocation based, in part, on the recently permitted NSSAI. The RAN 220 component can signal the AMF 205 component to redirect the registration request to the AMF 210 component. The redirection of the AMF 205 component request can include transmitting a redirect message and transmission can be through the component RAN 220 or via direct signaling between the AMF 2 05 component and the AMF 210 component (for example, through communication links 260). In some cases, the redirect message transmitted by the AMF component 2 05 through the RAN 22 0 component may include information for the selection of a new AMF to serve the UE 215.
[0118] According to a second technique, a network can trigger a new registration procedure. In some cases, the second technique may apply when a new set of allowed network slices does not overlap with the previous set of allowed network slices. Similarly, the AMF 205 component can be a current AMF that serves network slices used by the UE 215. These network slices can be associated with an NSSAI currently allowed. The AMF 205 component can receive a recently permitted NSSAI based on a change to the currently permitted NSSAI. In some cases, the AMF 205 component may determine to modify a currently allowed network slice used by the UE 215 based on the NSSAI
Petition 870190114669, of 11/08/2019, p. 66/172
62/117 recently allowed. In this way, the AMF 205 component can modify the currently permitted NSSAI used by the UE 215.
[0119] The AMF 205 component can select a new AMF based on the recently allowed NSSAI. In some cases, the AMF 205 component may determine that no new AMF can be selected or that the new AMF is not obtainable by the AMF 205 component. In that case, the AMF 205 component (that is, the current AMF) can transmit a deregistration request for UE 215. The deregistration request may include an indication to perform a re-registration procedure, the recently permitted NSSAI, or a code indicating that deregistration is in response to a change network slices supported in the recently permitted NSSAI, or a combination thereof.
[0120] The AMF 205 component may refrain from releasing an N2 signaling connection until the AMF 205 component receives a request from the RAN 220 component. In some cases, the RAN 220 component may transmit a request to the AMF 205 component to release the N2 signaling connection via communication link 260. In response to receiving the request from the RAN 220 component, the AMF 205 component can trigger a release procedure. The release procedure can be a PDU release procedure for each active PDU session associated with an S-NSSAI that is not supported in the recently allowed NSSAI. In some instances, when all active PDU sessions are released, the AMF 205 component can
Petition 870190114669, of 11/08/2019, p. 67/172
63/117 release the EU context for the AMF 210 component.
[0121] Returning to the case where the AMF 205 component transmits the deregistration request to the UE 215, the UE 215 can determine that the request is provided by the AMF 205 component and that the request includes a code indicating that the unregistration request is in response to a recently allowed NSSAI-supported network slice change. In addition, UE 215 can identify the recently permitted NSSAI based on the registration cancellation request received. In some cases, the UE 215 can store the newly permitted NSSAI locally or remotely, or both. UE 215 can also determine which network slices in the newly allowed NSSAI received to connect to. Based on the determination of which network slices to connect to, the UE 215 can generate an NSSAI request that identifies the network slices. The UE 215 can transmit the NSSAI request for the AMF component 2 05 or AMF 210 component, or both.
[0122] UE 215 can also perform operations based on the code received with the request to cancel the registration. UE 215 can remove a current NR GUTI based on the received code. Additionally or alternatively, an upper layer of UE 215 may transmit to a lower layer of UE 215: an indication to release a connection to the RAN 220 component and to reestablish the connection, or the NSSAI request, or an indication to abstain to provide a NR GUTI, or a combination thereof. In some instances, the
Petition 870190114669, of 11/08/2019, p. 68/172
64/117 top layer can be a NAS layer and the bottom layer can be an AS layer. In some cases, UE 215 may transmit a request to reestablish the connection based on the indication to reestablish the connection, where the request includes the NSSAI request. In some instances, the connection may be an RRC connection. In this case, the UE 215 can perform an RRC connection release procedure or an RRC connection establishment procedure, or both based on the indication to release a connection with a RAN 220 component and to reestablish the connection. Alternatively, the connection can be an IP security tunnel (TPsec) connection. In that case, the UE 215 can perform an IPsec tunnel release procedure or an IPsec tunnel establishment procedure, or both based on the indication to release a connection to an RAN and to reestablish the connection.
[0123] In some cases, the upper layer of UE 215 may transmit to the lower layer of UE 215 to modify a connection with the RAN 220 component, and provide the NSSAI request. The UE 215 can transmit a new RRC reconfiguration request message that includes the NSSAI request, or a code indicating the signaling path configuration, or a current NR GUTI, or a combination thereof. Alternatively, the UE 215 can transmit an Nwu message that includes the NSSAI request, or the code indicating the signaling path configuration, or the current NR GUTI, or a combination thereof. In some examples, the UE 215 may include a NAS registration request message in the
Petition 870190114669, of 11/08/2019, p. 69/172
65/117 RRC message, which provides the NSSAI request.
[0124] The RAN 220 component can receive an RRC request message that includes the NSSAI request from the UE 215. According to one technique, the RAN 220 component can select the AMF 210 component as a target AMF for serve UE 215 based on NSSAI received in the RRC request message. A connection between the RAN 220 component and the AMF 210 component can be established based on the selection of the AMF 210 component to serve the UE 215. For example, the RAN 220 component and the AMF 210 component can establish a connection through communication links 260. In some examples, as part of establishing the connection with the AMF 210 component, the RAN 220 component can transmit the NAS message received from the UE 215 to the AMF 210 component. In addition, the The connection established between the AMF 210 component and the RAN 22 0 component can be an N2 signaling connection.
[0125] According to another technique, the RAN 220 component can select the AMF 210 component as a target AMF to serve the UE 215 based on the NSSAI received in the RRC request message, and establish a connection with the AMF 210 component via communication links 260. In some cases, the RAN 220 component may transmit to the AMF 205 component (for example, now previous AMF) a request to release a connection; for example, an N2 signaling connection between the AMF 205 component and the RAN 220 or UE 215 component, or both. In some cases, the RAN 220 component may receive, from the MFA component
Petition 870190114669, of 11/08/2019, p. 70/172
66/117
210, an updated NR GUTI for UE 215, and replace a previous NR GUTI with the updated NR GUTI received for UE 215. The RAN 220 component can transmit the feedback (for example, results) of the record with the component ΑΜΕ 210 for UE 215. For example, feedback can include the updated NR GUTI and an indication that the AMF 210 component is a new serving AMF for UE 215 for network slices associated with the recently allowed NSSAI.
[0126] Figure 3 illustrates an example of a process flow 300 that supports the enabling of changing a network slice network trigger, according to one or more aspects of the present disclosure. In some examples, process flow 300 can implement aspects of wireless communications system 100 and 200. UE 305 can be an example of aspects of a respective UE 115 described with reference to Figures 1 or 2. The MFA component 310 and the AMF component 315 can be an example of aspects of a respective among the AMF components described with reference to Figure 2.
[0127] In the following description of process flow 300, operations between the UE 305, AMF 310 component or AMF 315 component can be transmitted in an order different from the example order shown, or the operations performed by the UE 305 component of AMF 310 or component of AMF 315 can be performed in different orders or at different times. Certain operations can also be left out of process flow 300, or other operations can be added to process flow 300.
Petition 870190114669, of 11/08/2019, p. 71/172
67/117
[0128] At 320, the ΑΜΕ 310 component can identify a request to modify the currently allowed network slice supported by the UE 305 based on a network trigger. In 325, the AMF 310 component can identify recently allowed network slices for the UE 305. In 330, the AMF 310 component can select a target AMF. In some examples, the AMF 310 component may select the target AMF based on the recently allowed network slices, where the target AMF is accessible by the source AMF. In some cases, the AMF 310 component may determine that the UE 305 has an NSI associated with at least one NSSAI of an S-NSSAI currently allowed, and identify that an active NSI is supported on the recently allowed network slices. In 335, the AMF 310 component can trigger an AMF relocation. In some examples, the AMF 310 component may trigger the relocation of AMF based on the selection of the target AMF. The AMF 310 component can transmit the AMF relocation request, at 340 to the AMF 315 component.
[0129] At 345, the AMF component 315 can allocate an NR GUTI. For example, the AMF 315 component can allocate the NR GUTI to the UE 305 based on the triggered AMF relocation. At 350, the AMF 315 component can transmit a configuration request message to the UE 305. The configuration request message can include the NR GUTI, an updated status of an existing EU PDU session (or multiple existing EU PDU sessions), or the recently allowed network slices, or a combination thereof. In some cases, the NR GUTI may be a version
Petition 870190114669, of 11/08/2019, p. 72/172
68/117 modified from a previous NR GUTI assigned to UE 305.
[0130] At 355, UE 305 can release PDU sessions. In some cases, the UE 305 may receive, from the AMF 310 component, the configuration message that includes the NR GUTI associated with an AMF 315 component, a situation from an existing active PDU session of the UE 305, or slices of recently allowed networks, or a combination of them. The UE 305 can store information associated with the recently allowed network slices and the NR GUTI. The UE 305 can identify an active PDU session based on the status of existing active PDU session information included in the configuration message, the identified active PDU session cannot be supported by the newly allowed network slices As a result, the UE 305 can release the identified PDU session locally. In some cases, the UE 305 may identify the local UE PDU session situation for one or more active PDU sessions. In addition, the UE 305 can receive the updated status associated with the UE PDU sessions. UE 305 can release the PDU sessions that were supported in the local UE PDU session situation, but are not supported in the updated situation received. For example, UE 305 can compare the local UE PDU session situation with the updated situation received. Based on the comparison, the UE 305 can identify a high in the EU PDU sessions. That is, UE 305 can identify that some or all PDU sessions associated with the local UE PDU session situation are no longer supported in the updated situation received. In that case, the UE 305 can release PDU sessions that are no longer
Petition 870190114669, of 11/08/2019, p. 73/172
69/117 supported. In addition, PDU sessions that are no longer supported may have already been released over the network.
[0131] Figure 4 illustrates an example of a process flow 400 that supports the enabling of changing a network slice network trigger, according to one or more aspects of the present disclosure. In some examples, process flow 400 may implement aspects of wireless communications system 100 and 200. UE 405 may be an example of aspects of a respective UE 115 described with reference to Figures 1 to 3. The MFA component 410 and the RAN component 415 can be an example of aspects of a respective among the AMF components and RAN component described with reference to Figure 2.
[0132] In the following description of process flow 400, operations between the UE 405, AMF 410 component or RAN 415 component can be transmitted in an order different from the example order shown, or the operations performed by the UE 405 component AMF 410 or RAN 415 component can be performed in different orders or at different times. Certain operations can also be left out of process flow 400, or other operations can be added to process flow 400.
[0133] In 420, the AMF 410 component can identify that it modifies the currently allowed network slice (or slices) used by the UE 405 based on a network trigger. In 425, the AMF 410 component can identify a recently allowed slice (or slices) of network for the UE 405. In 430, the AMF 410 component
Petition 870190114669, of 11/08/2019, p. 74/172
70/117 can identify a target MFA based on the recently allowed network slices. In some cases, the AMF 410 component may determine that the target AMF associated with the recently allowed network slices is inaccessible by the AMF 410 component. Alternatively, the AMF 410 component may determine that the target AMF associated with the network slices recently allowed is accessible by the AMF component 410. Additionally, the AMF component can determine that no new AMF can be selected. In 435, the AMF 410 component may transmit a deregistration request to the UE 405. In some cases, the AMF 410 component may transmit the deregistration request to the UE 405 based on the determination that the AMF target is inaccessible or that no target AMF can be selected by the AMF 410 component. The unregistration request may include an indication to perform a re-registration procedure, the recently allowed network slices identified or a code indicating that the unregistration request is in response to a change in supported network slices, or a combination of them.
[0134] In 440, UE 405 can identify recently allowed network slice (or slices). In some cases, the UE 405 may identify a recently allowed network slice (or slices) based on the deregistration request received. At 445, UE 405 can generate a request to register the set of network slices. UE 405 may, in some cases, generate the request to register the set of network slices based on the code. In 450, UE 405 transmits a request for
Petition 870190114669, of 11/08/2019, p. 75/172
71/117 record. The UE 405 can transmit the registration request to register the recently allowed network slice (or slices) for the RAN 415 component. In some instances, based on the code, the UE 405 can transmit the request without providing a GUTI to the RAN 415 component. In 455, the RAN 415 component can select a target AMF to serve the UE 405. In some cases, the RAN 415 component can select a target AMF to serve the UE 405 based on the request for record.
[0135] Figure 5 shows a block diagram 500 of a wireless device 505 that supports an enabling of a network slice switch trigger according to one or more aspects of the present disclosure. The wireless device 505 can be an example of aspects of a network entity AMF as described in this document. The wireless device 505 can include the receiver 510, network entity network slice manager 515, and transmitter 520. The device 505 can also include a processor. Each of these components can be in communication with each other (for example, through one or more buses).
[0136] Receiver 510 can receive information such as packets, user data, or control information associated with various information channels (for example, control channels, data channels, and related information to enable a change to the network trigger of network slices, etc.). The information can be passed on to other components of the device. The 510 receiver can be an example of aspects of the 835 transceiver described with reference to Figure 8. The 510 receiver can
Petition 870190114669, of 11/08/2019, p. 76/172
72/117 use a single antenna or set of antennas.
[0137] The network entity network slice manager 515 can be an example of aspects of the network entity network slice manager 815 described with reference to Figure 8.
[0138] The network slice manager of network entity 515 and / or at least some of its various subcomponents can be deployed in hardware, software run by a processor, firmware or any combination thereof. If deployed in software run by a processor, the functions of the network entity manager of network entity 515 and / or at least some of its various subcomponents can be performed by a general purpose processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC), a field programmable gate arrangement (FPGA) or other programmable logic device, discrete or transistor logic gate, discrete hardware components, or any combination of them designed to perform the functions described in the present revelation.
[0139] The network slice manager of network entity 515 and / or at least some of its various subcomponents may be physically located in various positions, including being distributed so that the portions of functions are deployed in different physical locations by one or more physical devices. In some instances, the network entity network slice manager 515 and / or at least some of the various subcomponents may be a separate or distinct component according to various aspects of the present disclosure. In other examples, the
Petition 870190114669, of 11/08/2019, p. 77/172
73/117 515 network entity network slice manager and / or at least some of its various subcomponents may be combined with one or more other hardware components, including, but not limited to, an I / O component, a transceiver , a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof according to various aspects of the present disclosure.
[0140] The network slice manager of network entity 515 can determine to modify the currently allowed network slices used by a UE based on a network trigger, identify the recently allowed network slices for the UE based on the determination , select a target AMF based on the recently allowed network slices, where the target AMF is accessible by the source AMF, and trigger an AMF relocation based on the selection. The network entity network slice manager 515 can also receive an AMF relocation request to an UE currently served by the source AMF from a source AMF. The MFA relocation request may include recently allowed network slices and UE context information. The network entity network slice manager 515 can allocate an updated GUTI to the UE based on the AMF relocation request; and transmit a configuration request message to the UE that includes the updated NR GUTI, an updated status of an existing PDU session, or the recently allowed NSSAI, or a combination thereof.
[0141] The network slice manager of network entity 515 can also determine to modify the
Petition 870190114669, of 11/08/2019, p. 78/172
74/117 currently allowed network slice used by a UE based on a received network trigger, identify the recently allowed network slices for the UE based on the determination, and determine that a target MFA associated with the recently allowed network slices it is inaccessible by the source AMF. The network entity network slice manager 515 can also receive, from a UE, an RRC connection request that includes NSSAI, select a target AMF to serve the UE based on the NSSAI received in the RRC connection request, establish an N2 signaling connection with the selected AMF, and transmit a NAS message received from the UE to the selected AMF using the N2 signaling connection.
[0142] The transmitter 520 can transmit signals generated by the other components of the device. In some examples, transmitter 520 may be colocalized with a receiver 510 on a transceiver module. For example, transmitter 520 can be an example of aspects of transceiver 835 described with reference to Figure 8. Transmitter 520 can use a single antenna or a set of antennas.
[0143] It should be noted that the methods described above describe possible deployments, and that operations and blocks can be rearranged or otherwise modified and that other deployments are possible. In addition, the aspects of two or more of the methods can be combined.
[0144] Figure 6 shows a block diagram 600 of a 605 wireless device that supports enabling a slice switch trigger
Petition 870190114669, of 11/08/2019, p. 79/172
75/117 network, according to one or more aspects of the present disclosure. The wireless device 605 can be an example of aspects of a wireless device 505 or an AMF as described with reference to Figure 5. The wireless device 605 can include receiver 610, network slice manager of network entity 615, and transmitter 620. The device 605 may also include a processor. Each of these components can be in communication with each other (for example, through one or more buses).
[0145] The 610 receiver can receive information such as packets, user data, or control information associated with various information channels (for example, control channels, data channels, and related information to enable a change to the network trigger of network slices, etc.). The information can be passed on to other components of the device. The receiver 610 can be an example of aspects of the transceiver 835 described with reference to Figure 8. The receiver 610 can use a single antenna or a set of antennas.
[0146] The network entity network slice manager 615 can be an example of aspects of the network entity network slice manager 815 described with reference to Figure 8. The network entity network slice manager 615 also may include network slice modification component 625, network slice identification component 630, AMF determination component 635, AMF relocation trigger component 640, request component 645, allocation component 650 and connection component 655 .
[0147] The slice modification component of
Petition 870190114669, of 11/08/2019, p. 80/172
76/117 network 625 can determine to modify the currently allowed network slices used by a UE based on a network trigger and determine to modify the currently allowed network slice used by a UE based on a received network trigger. The network slice identification component 630 can identify recently allowed network slices for the UE that is based on the determination, determine that the UE has an active network slice (NSI) instance associated with at least one selection assistance information (NSSAI), and identify that an active NSI is supported by the recently allowed network slices.
[0148] The AMF determination component 635 can select a target AMF based on the recently allowed network slices, where the target AMF is accessible by the source AMF. The AMF determination component 635 may determine that a target AMF associated with the recently allowed network slices is inaccessible by the source AMF, and transmit a deregistration request to the UE based on the determination that the target AMF is inaccessible by the MFA-source. The AMF determination component 635 can select a target AMF to serve the UE based on the NSSAI received in the RRC connection request. The AMF determination component 635 can receive, from the selected AMF, an updated NR GUTI for the UE, and replace a previous NR GUTI with the updated NR GUTI received for the UE. In some cases, the deregistration request includes an indication to perform a re-registration procedure, the recently allowed network slices identified or
Petition 870190114669, of 11/08/2019, p. 81/172
77/117 a code that indicates that the unregistration request is in response to a change in supported network slices, or a combination of them.
[0149] The AMF relocation trigger component 640 can trigger an AMF relocation based on selection and transmit an AMF relocation request to the target AMF based on the recently allowed NSSAI, where the AMF relocation request includes a status of the entire existing PDU session associated with the active NSI that is supported and active, or a globally unique temporary identifier (GUTI) of NR, or both.
[0150] Request component 645 may receive, from a source AMF, an AMF relocation request to a UE currently served by the source AMF, and the AMF relocation request includes new allowed network slices and information from EU context. Request component 645 can transmit a configuration request message to the UE that includes the updated NR GUTI, an updated situation from an existing PDU session, or the recently allowed NSSAI, or a combination thereof, and receive from a UE, an RRC connection request that includes the NSSAI. In some cases, UE context information includes a situation from an existing PDU session associated with an active NSI or a current NR GUTI, or a combination thereof. The allocation component 650 can allocate an updated NR GUTI to the UE based on the AMF relocation request.
[0151] Connection component 655 can
Petition 870190114669, of 11/08/2019, p. 82/172
78/117 establish an N2 signaling connection with the selected AMF, transmit a NAS message received from the UE to the selected AMF using the N2 signaling connection, and transmit, to a previous UE server AMF, a request to release an N2 signaling connection.
[0152] The transmitter 620 can transmit signals generated by the other components of the device. In some examples, transmitter 620 can be colocalized with a receiver 610 on a transceiver module. For example, transmitter 620 may be an example of aspects of transceiver 835 described with reference to Figure 8. Transmitter 620 may use a single antenna or set of antennas.
[0153] Figure 7 shows a block diagram 700 of a network entity network slice manager 715 that supports an enabling of a network slice network trigger change, according to one or more aspects of the present disclosure. . The network entity network slice manager 715 can be an example of aspects of a network entity network slice manager 515, a network entity network slice manager 615, or a network slice manager of network network entity 815 described with reference to Figures 5, 6 and 8. Network entity network slice manager 715 may include network slice modification component 720, network slice identification component 725, component determination AMF 730, relocation trigger component of AMF 735, request component 740, allocation component 745, component of
Petition 870190114669, of 11/08/2019, p. 83/172
79/117 connection 750, report component 755 and release component 760. Each of these modules can communicate, directly or indirectly, with each other (for example, through one or more buses).
[0154] The network slice modification component 720 can determine to modify the currently allowed network slices used by a UE based on a network trigger and determine that it modify the currently allowed network slice used by a UE based on a network trigger received.
[0155] The network slice identification component 725 can identify newly allowed network slices for the UE that is based on the determination, determine that the UE has an active network slice (NSI) instance associated with at least one information network selection assistance (NSSAI), and identifying that an active NSI is supported by the recently allowed network slices.
[0156] The AMF determination component 730 can select a target AMF based on the recently allowed network slices, where the target AMF is accessible by the source AMF, determine that a target AMF associated with the recently allowed network slices is inaccessible by AMFfonte, and to transmit a deregistration request to the UE based on the determination that AMFalvo is inaccessible by the source AMF. The AMF determination component 730 can select a target AMF to serve the UE based on the NSSAI received in the RRC connection request. The AMF determination component 730 can receive, from the selected AMF, an updated NR GUTI
Petition 870190114669, of 11/08/2019, p. 84/172
80/117 for the UE, and replace a previous NR GUTI with the updated NR GUTI received for the UE. In some cases, the deregistration request includes an indication to perform a re-registration procedure, the recently allowed network slices identified, or a code indicating that the deregistration request is in response to a change in the network slices supported, or a combination of them.
[0157] The AMF relocation trigger component 735 can trigger an AMF relocation based on the selection and transmit an AMF relocation request to the target AMF based on the recently allowed NSSAI, where the AMF relocation request includes a status of the entire existing PDU session associated with the active NSI that is supported and active, or a NR GUTI, or both.
[0158] Request component 740 can receive, from a source AMF, an AMF relocation request to an UE currently served by the source AMF, the AMF relocation request includes recently allowed network slices and information from context of UE, and transmit to the UE a configuration request message that includes the updated NR GUTI, an updated status of an existing PDU session, or the recently allowed NSSAI, or a combination thereof. Request component 740 can receive an RRC connection request that includes NSSAI from a UE. In some cases, UE context information includes a situation from an existing PDU session associated with an active NSI or a current NR GUTI, or a combination thereof.
Petition 870190114669, of 11/08/2019, p. 85/172
81/117
[0159] The allocation component 745 can allocate an updated NR GUTI to the UE based on the AMF relocation request. Connection component 750 can establish an N2 signaling connection with the selected AMF, transmit a NAS message received from the UE to the selected AMF using the N2 signaling connection, and transmit to a previous UE server AMF , a request to release an N2 signaling connection. The 755 reporting component can generate a progress report that indicates a status for all existing PDU sessions associated with the active NSI.
[0160] Release component 760 can trigger a procedure for releasing an active PDU session associated with the currently allowed network slices based on the identification that the active PDU session is not supported by the recently allowed network slices, triggering a procedure for releasing an active PDU session associated with currently allowed network slices that ~ are not supported by the recently allowed network slices, and releasing the UE context that includes an active PDU session progress report or an NR GUTI , or both based on the trigger. In some cases, the triggering of the release procedure is based on direct signaling to the UE.
[0161] Figure 8 shows a diagram of a system 800 that includes a device 805 that supports enabling a network trigger change of network slices, according to one or more aspects of the present disclosure. The 805 device can be an example or include the wireless device components 505, wireless device
Petition 870190114669, of 11/08/2019, p. 86/172
82/117 wire 605 or an AMF, as described above, for example, with reference to Figures 5 and 6. The 805 device may include components for two-way voice and data communications that include components for transmitting and receiving communications, including slice manager network entity 815, processor 820, memory 825, software 830, transceiver 835 and I / O controller 840. These components can be in electronic communication via one or more buses (for example, bus 810).
[0162] The 820 processor may include an intelligent hardware device, (for example, a general purpose processor, a DSP, a central processing unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the 820 processor can be configured to operate a memory array using a memory controller. In other cases, a memory controller can be integrated into the 820 processor. The 820 processor can be configured to execute computer-readable instructions stored in memory to perform various functions (for example, functions or tasks that support enabling an network slice network trigger).
[0163] Memory 825 can include random access memory (RAM) and read-only memory (ROM). The 825 memory can store 830 computer-readable, computer-readable software that includes
Petition 870190114669, of 11/08/2019, p. 87/172
83/117 instructions that, when executed, cause the processor to perform several functions described in this document. In some cases, the 825 memory may contain, among other things, a basic input-output system (BIOS) that can control the operation of basic hardware or software such as interaction with peripheral components or devices. The 830 software may include code to implement aspects of the present disclosure, including code to support enabling a network slice change of network trigger. The 830 software can be stored on a non-transitory computer-readable medium such as system memory or other memory. In some cases, the 830 software may not be directly executable by the processor, but it can cause a computer (for example, when compiled and run) to perform functions described in this document.
[0164] The 835 transceiver can communicate bidirectionally through one or more antennas, with wired or wireless links as described above. For example, the 835 transceiver can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The 835 transceiver may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.
[0165] The I / O controller 840 can manage input and output signals for the 805 device. The I / O controller 840 can also manage peripherals not integrated in the 805 device. In some cases, the I / O controller 840 can represent a physical connection
Petition 870190114669, of 11/08/2019, p. 88/172
84/117 or port to an external peripheral. In some cases, the 840 I / O controller may use an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system . In other cases, the 840 I / O controller can represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the 840 I / O controller can be deployed as part of a processor. In some cases, a user can interact with the 805 device through the I / O controller 840 or through hardware components controlled by the I / O controller 840.
[0166] Figure 9 shows a block diagram 900 of a wireless device 905 that supports an enabling of a network slice switch trigger according to one or more aspects of the present disclosure. The wireless device 905 can be an example of aspects of an UE 115 as described in this document. The wireless device 905 can include the receiver 910, UE 915 network slice manager and transmitter 920. The device 905 can also include a processor. Each of these components can be in communication with each other (for example, through one or more buses).
[0167] The 910 receiver can receive information such as packets, user data, or control information associated with various information channels (for example, control channels, data channels, and related information to enable a change to the network trigger of network slices, etc.). Information can be
Petition 870190114669, of 11/08/2019, p. 89/172
85/117 passed on to other device components. The receiver 910 can be an example of aspects of the transceiver 1235 described with reference to Figure 12. The receiver 910 can use a single antenna or a set of antennas. The UE 915 network slice manager can be an example of aspects of the UE 1215 network slice manager described with reference to Figure 12.
[0168] The UE 915 network slice manager and / or at least some of its various subcomponents can be deployed in hardware, software run by a processor, firmware or any combination thereof. If deployed in software run by a processor, the functions of the UE 915 network slice manager and / or at least some of its various subcomponents can be performed by a general purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.
[0169] The UE 915 network slice manager and / or at least some of its various subcomponents may be physically located in various positions, including being distributed so that the portions of functions are deployed in different physical locations by one or more physical devices. In some instances, the UE 915 network slice manager and / or at least some of the various subcomponents may be a separate or distinct component according to various aspects of the present disclosure. In other examples, the
Petition 870190114669, of 11/08/2019, p. 90/172
86/117 UE 915 network slice and / or at least some of its various subcomponents may be combined with one or more other hardware components, including, but not limited to, an I / O component, a transceiver, a server network, another computing device, one or more other components described in the present disclosure, or a combination thereof according to various aspects of the present disclosure.
[0170] The UE 915 network slice manager can receive, from an AMF-source, a configuration message that includes an NR GUTI associated with an AMFtarget, an existing active PDU session situation from the UE, or slices recently allowed network connections, or a combination thereof, store information associated with the recently allowed network slices and NR GUTI, identify an active PDU session based on the existing active PDU session status information included in the configuration message, the identified active PDU session is not supported by the recently allowed network slices, and locally release the identified active PDU session. The UE 915 network slice manager can also identify a request for new registration and a code that indicates a request to register a set of network slices associated with a recently allowed network slice based on a deregistration request received from a source AMF serving the UE, identify new allowed network slices based on the unregistration request received, and generate a request to register the set of network slices based on the code.
Petition 870190114669, of 11/08/2019, p. 91/172
87/117
[0171] The 920 transmitter can transmit signals generated by the other components of the device. In some examples, transmitter 920 can be colocalized with a 910 receiver on a transceiver module. For example, transmitter 920 can be an example of aspects of transceiver 1235 described with reference to Figure 12. Transmitter 920 can use a single antenna or a set of antennas.
[0172] Figure 10 shows a block diagram 1000 of a wireless device 1005 that supports an enabling of a network slice switch trigger, according to one or more aspects of the present disclosure. The wireless device 1005 can be an example of aspects of a wireless device 905 or an UE 115 as described with reference to Figure 9. The wireless device 1005 can include the receiver 1010, UE 1015 network slice manager and transmitter. 1020. The device 1005 can also include a processor. Each of these components can be in communication with each other (for example, through one or more buses).
[0173] The 1010 receiver can receive information such as packets, user data, or control information associated with various information channels (for example, control channels, data channels, and related information to enable a change to the network trigger of network slices, etc.). The information can be passed on to other components of the device. The receiver 1010 can be an example of aspects of the transceiver 1235 described with reference to Figure 12. The receiver 1010 can use a single antenna or a set
Petition 870190114669, of 11/08/2019, p. 92/172
88/117 antennas.
[0174] The UE 1015 network slice manager can be an example of aspects of the UE 1215 network slice manager described with reference to Figure 12. The UE 1015 network slice manager can also include 1025 configuration component , session component 1030, release component 1035, request component 1040 and network slice identification component 1045.
[0175] The configuration component 1025 can receive, from a source AMF, a configuration message that includes a NR GUTI associated with a target AMF, a situation from an existing active PDU session of the UE, or network slices recently allowed, or a combination thereof, and store information associated with the recently allowed network slices and NR GUTI. The 1030 session component can identify an active PDU session based on the status of existing active PDU session information included in the configuration message, the identified active PDU session is not supported by the recently allowed network slices.
[0176] The 1035 release component can release the identified active PDU session locally. The 1040 request component can identify a new registration request and a code that indicates a request to register a set of network slices associated with a recently allowed network slice based on a deregistration request received from a source AMF. that is serving the UE and generate a request to register the set of network slices
Petition 870190114669, of 11/08/2019, p. 93/172
89/117 based on the code.
[0177] The network slice identification component 1045 can identify recently allowed network slices based on the unregistration request received, store information associated with recently allowed network slices, where the information includes NSSAI, and remove a Current NR GUTI based on code.
[0178] The 1020 transmitter can transmit signals generated by the other components of the device. In some examples, transmitter 1020 can be colocalized with a receiver 1010 on a transceiver module. For example, transmitter 1020 can be an example of aspects of transceiver 1235 described with reference to Figure 12. Transmitter 1020 can use a single antenna or a set of antennas.
[0179] Figure 11 shows a block diagram 1100 of an EU 1115 network slice manager that supports an enabling of a network slice network trigger change, according to one or more aspects of the present disclosure. The UE 1115 network slice manager can be an example of aspects of an UE 1215 network slice manager described with reference to Figures 9, 10 and 12. The UE 1115 network slice manager can include 1120 configuration component , session component 1125, release component 1130, request component 1135, network slice identification component 1140 and connection component 1145. Each of these modules can communicate, directly or indirectly, with each other (for example, through one or more buses).
Petition 870190114669, of 11/08/2019, p. 94/172
90/117
[0180] Configuration component 1120 can receive, from a source AMF, a configuration message that includes a NR GUTI associated with a target AMF, a situation from an existing active PDU session of the UE, or network slices recently allowed, or a combination thereof, and store information associated with the recently allowed network slices and NR GUTI. Session component 1125 can identify an active PDU session based on the status of existing active PDU session information included in the configuration message, the identified active PDU session is not supported by the recently allowed network slices. Release component 1130 can locally release the identified active PDU session.
[0181] Request component 1135 can identify a new registration request and a code that indicates a request to register a set of network slices associated with a recently allowed network slice based on a deregistration request received from a management and access function (AMF) source that is serving the UE and generate a request to register the set of network slices based on the code. The network slice identification component 1140 can identify recently allowed network slices based on the received deregistration request, store information associated with recently allowed network slices, where the information includes NSSAI, and remove a NR GUTI current based on code.
[0182] Connection component 1145 can transmit a request to reestablish the connection based on the indication to reestablish the connection, where the
Petition 870190114669, of 11/08/2019, p. 95/172
91/117 request includes the NSSAI request, and transmit a new RRC reset request message that includes the NSSAI request, or a code indicating the signaling path configuration, or a current NR GUTI, or combination of the same. The connection component 1145 can transmit an Nwu message that includes the NSSAI request, or a code indicating the signaling path configuration, or a current NR GUTI, or a combination thereof. In some cases, an upper UE transmits to a lower layer of the UE: an indication to release a connection to a RAN and reestablish the connection, or the NSSAI request, or an indication to refrain from providing an NR GUTI, or a combination of them. In some cases, the top layer includes a NAS layer and the bottom layer includes an AS layer. In some cases, the connection includes an RRC connection. In some cases, the UE performs an RRC connection release procedure or an RRC connection establishment procedure, or both based on the indication to release a connection to an RAN and to reestablish the connection. In some cases, the connection includes a tunnel connection (TPsec). In some cases, the UE performs a TPsec tunnel release procedure or a TPsec tunnel establishment procedure, or both based on the indication to release a connection to a RAN and to reestablish the connection. In some cases, the Nwu message includes an IKEV2 INFORMATION message, or a reconfiguration signal connection message, or both.
[0183] Figure 12 shows a diagram of a
Petition 870190114669, of 11/08/2019, p. 96/172
92/117 system 1200 which includes a device 1205 which supports enabling a network trigger change of network slices, in accordance with one or more aspects of the present disclosure. Device 1205 can be an example of or include components of UE 115 as described above, for example, with reference to Figure 1. Device 1205 can include components for two-way voice and data communications that include components for transmitting and receiving communications, including UE 1215 network slice manager, processor 1220, memory 1225, software 1230, transceiver 1235, antenna 1240, and I / O controller 1245. These components can be in electronic communication via one or more buses (for example , bus 1210). Device 1205 can communicate wirelessly with one or more base stations 105.
[0184] The 1220 processor may include an intelligent hardware device, (for example, a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete port or logic component transistor, a discrete hardware component or any combination thereof). In some cases, the 1220 processor can be configured to operate a memory array using a memory controller. In other cases, a memory controller can be integrated into the 1220 processor. The 1220 processor can be configured to execute computer-readable instructions stored in memory to perform various functions (for example, functions or tasks that support enabling an network slice network trigger).
Petition 870190114669, of 11/08/2019, p. 97/172
93/117
[0185] Memory 1225 can include RAM and ROM.
Memory 1225 can store computer-executable, computer-readable 1230 software that includes instructions that, when executed, cause the processor to perform various functions described in this document. In some cases, memory 1225 may contain, among other things, a BIOS that can control the operation of basic hardware or software such as interaction with peripheral components or devices.
[0186] The 1230 software may include code to implement aspects of the present disclosure, including code to support the enabling of a network slice switch trigger. The 1230 software can be stored in a non-transitory, computer readable medium such as system memory or other memory. In some cases, the 1230 software may not be directly executable by the processor, but it can cause a computer (for example, when compiled and run) to perform functions described in this document.
[0187] Transceiver 1235 can communicate bidirectionally through one or more antennas, with wired or wireless links as described above. For example, transceiver 1235 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The 1235 transceiver may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas. In some cases, the wireless device may include a single 1240 antenna. However, in some cases, the device may have more than
Petition 870190114669, of 11/08/2019, p. 98/172
94/117 an antenna 1240, which may have the ability to transmit or receive multiple wireless transmissions simultaneously.
[0188] The I / O controller 1245 can manage input and output signals for the 1205 device. The I / O controller 1245 can also manage peripherals not integrated in the 1205 device. In some cases, the I / O controller 1245 it can represent a physical connection or port to an external peripheral. In some cases, the 1245 I / O controller may use an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system . In other cases, the 1245 I / O controller can represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the 1245 I / O controller can be deployed as part of a processor. In some cases, a user can interact with the 1205 device via the I / O controller 1245 or through hardware components controlled by the I / O controller 1245.
[0189] Figure 13 shows a flowchart that illustrates a 1300 method to enable a change of the network slice network trigger, according to one or more aspects of the present disclosure. Method 1300 operations can be implemented by an MFA or its components, as described in this document. For example, method 1300 operations can be performed by a network entity network slice manager as described with reference to Figures 5 to 8. In some examples, a network entity can execute a set of codes to control the elements functional
Petition 870190114669, of 11/08/2019, p. 99/172
95/117 device 115 to perform the functions described below. Additionally or alternatively, the network entity may perform aspects of the functions described below using hardware for specific purposes.
[0190] In 1305, the network entity may determine to modify the recently allowed network slices used by a UE based on a network trigger. 1305 operations can be performed according to the methods described in this document. In certain examples, aspects of 1305 operations can be performed by a network slice modification component as described with reference to Figures 5 to 8.
[0191] In 1310, the network entity can identify recently allowed network slices for the UE based on the determination. 1310 operations can be performed according to the methods described in this document. In certain examples, aspects of 1310 operations can be performed by a network slice identification component as described with reference to Figures 5 to 8.
[0192] In 1315, the network entity can select a target AMF based on the recently allowed network slices, the target AMF is accessible by the AMF source. 1315 operations can be performed according to the methods described in this document. In certain examples, aspects of 1315 operations can be performed by an AMF determination component as described with reference to Figures 5 to 8.
[0193] In 1320, the network entity may trigger a relocation of MFA based on selection. At
Petition 870190114669, of 11/08/2019, p. 100/172
96/117 1320 operations can be performed according to the methods described in this document. In certain examples, aspects of 1320 operations can be performed by an MFA relocation trigger component as described with reference to Figures 5 to 8.
[0194] Figure 14 shows a flowchart that illustrates a 1400 method to enable a change of the network slice network trigger, according to one or more aspects of the present disclosure. The 1400 method operations can be implemented by a network entity, for example, AMF or its components, as described in this document. For example, method 1400 operations can be performed by a network entity network slice manager as described with reference to Figures 5 to 8. In some examples, a network entity can execute a set of codes to control the elements device 115 to perform the functions described below. Additionally or alternatively, the network entity may perform aspects of the functions described below using hardware for specific purposes.
[0195] In 1405, the network entity may receive, from a source AMF, an AMF relocation request to a UE currently served by the source AMF, the AMF relocation request includes new allowed network slices and EU context information. 1405 operations can be performed according to the methods described in this document. In certain examples, aspects of 1405 operations can be
Petition 870190114669, of 11/08/2019, p. 101/172
97/117 performed by a request component as described with reference to Figures 5 to 8.
[0196] In 1410, the network entity may allocate an updated NR GUTTI to the UE based on the AMF relocation request. 1410 operations can be performed according to the methods described in this document. In certain examples, aspects of the 1410 operations can be performed by an allocation component as described with reference to Figures 5 to 8.
[0197] In 1415, the network entity may transmit a configuration request message to the UE that includes the updated NR GUTI, an updated status of an existing PDU session, or the recently allowed NSSAI, or a combination thereof . 1415 operations can be performed according to the methods described in this document. In certain examples, aspects of the 1415 operations can be performed by a request component as described with reference to Figures 5 to 8.
[0198] Figure 15 shows a flowchart that illustrates a 1500 method to enable a change of the network slice network trigger, according to one or more aspects of the present disclosure. Method 1500 operations can be deployed by an UE 115 or its components, as described in this document. For example, method 1500 operations can be performed by an UE network slice manager as described with reference to Figures 9 to 12. In some examples, an UE 115 can execute a set of codes to control the functional elements of the device 115 to perform the
Petition 870190114669, of 11/08/2019, p. 102/172
98/117 functions described below. Additionally or alternatively, the UE 115 can perform aspects of the functions described below using hardware for specific purposes.
[0199] In 1505, the UE 115 can receive, from a source AMF, a configuration message that includes a NR GUTTI associated with a target AMF, a situation from an existing active PDU session of the UE 115, or slices recently allowed network connections, or a combination of them. 1505 operations can be performed according to the methods described in this document. In certain examples, aspects of the 1505 operations can be performed by a configuration component as described with reference to Figures 9 to 12.
[0200] In 1510, the UE 115 can store information associated with the recently allowed network slices and NR GUTI. The 1510 operations can be performed according to the methods described in this document. In certain examples, aspects of the 1510 operations can be performed by a configuration component as described with reference to Figures 9 to 12.
[0201] In 1515, the UE 115 can identify an active PDU session based on the status of existing active PDU session information included in the configuration message, the identified active PDU session is not supported by the recently allowed network slices. The 1515 operations can be performed according to the methods described in this document. In certain examples, aspects of 1515 operations can be performed by a session component as described
Petition 870190114669, of 11/08/2019, p. 103/172
99/117 with reference to Figures 9 to 12.
[0202] In 1520, the UE 115 can locally release the active PDU session identified. The 1520 operations can be carried out according to the methods described in this document. In certain examples, aspects of 1520 operations can be performed by a release component as described with reference to Figures 9 to 12.
[0203] Figure 16 shows a flowchart that illustrates a 1600 method to enable a change of network slices network trigger, according to one or more aspects of the present disclosure. The 1600 method operations can be implemented by a network entity, for example, AMF or its components, as described in this document. For example, the 1600 method operations can be performed by a network entity network slice manager as described with reference to Figures 5 to 8. In some examples, a network entity can execute a set of codes to control the elements device 115 to perform the functions described below. Additionally or alternatively, the network entity may perform aspects of the functions described below using hardware for specific purposes.
[0204] In 1605, the network entity may determine to modify the recently allowed network slice used by a UE based on a received network trigger. 1605 operations can be performed according to the methods described in this document. In certain examples, aspects of 1605 operations
Petition 870190114669, of 11/08/2019, p. 104/172
100/117 can be performed by a network slice modification component as described with reference to Figures 5 to 8.
[0205] In 1610, the network entity can identify recently allowed network slices for the UE based on the determination. 1610 operations can be performed according to the methods described in this document. In certain examples, aspects of the 1610 operations can be performed by a network slice identification component as described with reference to Figures 5 to 8.
[0206] In 1615, the network entity may determine that a target AMF associated with the recently allowed network slices is inaccessible by the source AMF. The 1615 operations can be performed according to the methods described in this document. In certain examples, aspects of the 1615 operations can be performed by an AMF determination component as described with reference to Figures 5 to 8.
[0207] In 1620, the network entity may identify a request for new registration and a code indicating a request to register a set of network slices associated with a recently allowed network slice based on a deregistration request received from a source AMF that is serving the UE. 1620 operations can be performed according to the methods described in this document. In certain examples, aspects of 1620 operations can be performed by a request component as described with reference to Figures 5 to 8.
Petition 870190114669, of 11/08/2019, p. 105/172
101/117
[0208] In 1625, the network entity can identify recently allowed network slices based on the deregistration request received. The 1625 operations can be carried out according to the methods described in this document. In certain examples, aspects of the 1625 operations can be performed by a network slice identification component as described with reference to Figures 5 to 8.
[0209] In 1630, the network entity may generate a request to register the set of network slices based on the code. 1630 operations can be performed according to the methods described in this document. In certain examples, aspects of the 1630 operations can be performed by a request component as described with reference to Figures 5 to 8.
[0210] Figure 17 shows a flowchart that illustrates a 1700 method to enable a network trigger change of network slices, according to one or more aspects of the present disclosure. The 1700 method operations can be deployed by an UE 115 or its components, as described in this document. For example, method 1700 operations can be performed by an UE network slice manager as described with reference to Figures 9 to 12. In some examples, an UE 115 can execute a set of codes to control the functional elements of the device 115 to perform the functions described below. Additionally or alternatively, the UE 115 can perform aspects of the functions described below using hardware for specific purposes.
Petition 870190114669, of 11/08/2019, p. 106/172
102/117
[0211] In 1705, the UE 115 may receive a deregistration request from a source AMF. In some cases, the UE 115 may identify a request for new registration and a code indicating a request to register one or more new network slices associated with a recently allowed network slice based on the unregister request received from AMF source that serves the UE 115. 1705 operations can be performed according to the methods described in this document. In certain examples, aspects of 1705 operations can be performed by a request component as described with reference to Figures 9 to 12.
[0212] In 1710, the UE 115 may generate a request to register one or more network slices based on a code (for example, which indicates a request to register one or more new network slices associated with a network slice recently allowed), where an upper layer of the UE transmits to a lower layer of the UE: an indication to release a connection to a RAN and to reestablish the connection, or an NSSAI request, or an indication to refrain from providing a GUTI of NR, or a combination thereof. Additionally, in some instances, upon receipt by the UE 115 of the deregistration request that includes an indication for the new registration or the cause code, or both; the upper layer (or layers) of the UE 115 may indicate to the lower layer (or layers) of the UE 115 that it erases an existing GUTI. In addition, the top layer (or layers) can indicate to the bottom layer (or layers) that it transmits
Petition 870190114669, of 11/08/2019, p. 107/172
103/117 a registration request with one or more new network slices. In some cases, the top layer is the NAS layer and the bottom layer is an AS layer. 1710 operations can be performed according to the methods described in this document. In certain examples, aspects of 1710 operations can be performed by a connecting component as described with reference to Figures 9 to 12.
[0213] In 1715, UE 115 can transmit a request to reestablish the connection based on the indication to reestablish the connection. In some cases, the request may include an NSSAI request. In some cases, the connection can also be an RRC connection. In this case, the UE 115 can perform an RRC connection release procedure or an RRC connection establishment procedure, or both based on the indication to release a connection to an RAN and to reestablish the connection. Alternatively, the connection can be an IPsec tunnel connection. In this case, the UE 115 can perform an IPsec tunnel release procedure or a
IPsec, or both based on the indication to release a connection to a RAN and to reestablish the connection. The 1715 operations can be carried out according to the methods described in this document. In certain examples, aspects of the 1715 operations can be performed by a connecting component as described with reference to Figures 9 to 12.
[0214] Figure 18 shows a flow chart that illustrates a 1800 method to enable a change in
Petition 870190114669, of 11/08/2019, p. 108/172
104/117 network slices network trigger, according to one or more aspects of the present disclosure. 1800 method operations can be implemented by a network entity, for example, RAN or its components, as described in this document. For example, the 1800 method operations can be performed by a network entity network slice manager as described with reference to Figures 5 to 8. In some examples, a network entity can execute a set of codes to control the elements device 115 to perform the functions described below. Additionally or alternatively, the network entity may perform aspects of the functions described below using hardware for specific purposes.
[0215] In 1805, the network entity may receive, from a UE, an RRC connection request that indicates a request to register one or more new network slices associated with a recently allowed NSSAI network slice. 1805 operations can be performed according to the methods described in this document. In certain examples, aspects of the 1805 operations can be performed by a request component as described with reference to Figures 5 to 8.
[0216] In 1810, the network entity may select a target AMF to serve the UE based on the NSSAI received in the RRC connection request. The 1810 operations can be carried out according to the methods described in this document. In certain examples, aspects of the 1810 operations can be carried out by
Petition 870190114669, of 11/08/2019, p. 109/172
105/117 an AMF determination component as described with reference to Figures 5 to 8.
[0217] In 1815, the network entity can establish an N2 signaling connection with the selected AMF. The 1815 operations can be carried out according to the methods described in this document. In certain examples, aspects of the 1815 operations can be performed by a connecting component as described with reference to Figures 5 to 8.
[0218] In 1820, the network entity can transmit a NAS message received from the UE to the selected AMF using the N2 signaling connection. 1820 operations can be performed according to the methods described in this document. In certain examples, aspects of the 1820 operations can be performed by a connecting component as described with reference to Figures 5 to 8.
[0219] Figure 19 shows a flowchart illustrating a 1900 method to enable a change in the network trigger of network slices, according to one or more aspects of the present disclosure. The 1900 method operations can be implemented by a network entity, for example, RAN or its components, as described in this document. In some examples, a network entity may execute a set of codes to control the functional elements of the device 115 to perform the functions described below. Additionally or alternatively, the network entity may perform aspects of the functions described below using hardware for specific purposes.
Petition 870190114669, of 11/08/2019, p. 110/172
106/117
[0220] In 1905, the network entity may receive, from a UE, an RRC connection request that includes NSSAI. 1905 operations can be carried out according to the methods described in this document. In certain examples, the network entity may perform aspects of the functions described below using special purpose hardware.
[0221] In 1910, the network entity can identify a source MFA associated with the currently allowed network slices of the UE based on the NSSAI. 1910 operations can be carried out according to the methods described in this document. In certain examples, the network entity may perform aspects of the functions described below using special purpose hardware.
[0222] In 1915, the network entity may determine that the NSSAI be modified based on a trigger indication. The 1915 operations can be carried out according to the methods described in this document. In certain examples, the network entity may perform aspects of the functions described below using special purpose hardware.
[0223] In 1920, the network entity can identify recently allowed network slices supported for the UE based on the determination. 1920 operations can be performed according to the methods described in this document. In certain examples, the network entity may perform aspects of the functions described below using special purpose hardware.
[0224] In 1925, the network entity may select a target MFA to serve the UE based on
Petition 870190114669, of 11/08/2019, p. 111/172
107/117 recently allowed network slices. The 1925 operations can be carried out according to the methods described in this document. In certain examples, the network entity may perform aspects of the functions described below using special purpose hardware.
[0225] In 1930, the network entity may trigger an AMF relocation based on the selection, the AMF relocation includes signaling the source AMF to redirect the RRC connection request to AMFalvo. The 1925 operations can be carried out according to the methods described in this document. In certain examples, the network entity may perform aspects of the functions described below using special purpose hardware.
[0226] Figure 20 shows a flowchart that illustrates a method 2000 to enable a change of network slices network trigger, according to one or more aspects of the present disclosure. Method 2000 operations can be implemented by a network entity, for example, RAN or its components, as described in this document. In some examples, a network entity may execute a set of codes to control the functional elements of the device 115 to perform the functions described below. Additionally or alternatively, the network entity may perform aspects of the functions described below using hardware for specific purposes.
[0227] In 2005, the network entity may receive, from a UE, a request for relocation of a source AMF associated with the network slices currently
Petition 870190114669, of 11/08/2019, p. 112/172
108/117 allowed from UE based on NSSAI. The 2005 operations can be carried out according to the methods described in this document. In certain examples, the network entity may perform aspects of the functions described below using special purpose hardware.
[0228] In 2010, the network entity may determine to modify the NSSAI based on a trigger indication. The 2010 operations can be carried out according to the methods described in this document. In certain examples, the network entity may perform aspects of the functions described below using special purpose hardware.
[0229] In 2015, the network entity can identify recently allowed network slices supported for the UE based on the determination. 2015 operations can be carried out according to the methods described in this document. In certain examples, the network entity may perform aspects of the functions described below using special purpose hardware.
[0230] In 2020, the network entity may select a target MFA to serve the UE based on the recently allowed network slices. 2020 operations can be carried out according to the methods described in this document. In certain examples, the network entity may perform aspects of the functions described below using special purpose hardware.
[0231] In 2025, the network entity may trigger an AMF relocation based on the selection, the AMF relocation includes initiating a redirection of the UE from the source AMF to the target AMF. The 2025 operations may
Petition 870190114669, of 11/08/2019, p. 113/172
109/117 be carried out according to the methods described in this document. In certain examples, the network entity may perform aspects of the functions described below using special purpose hardware.
[0232] The techniques described in this document can be used for various wireless communication systems such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA) and other systems. The terms system and network are often used interchangeably. A code division multiple access (CDMA) system can deploy radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers the IS-2000, IS-95 and IS-856 standards. Versions of IS2000 can be commonly referred to as CDMA2000 IX, IX, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 IxEV-DO, High Rate Data Package (HRPD), etc. UTRA includes Broadband CDMA (WCDMA) and other CDMA variants. A TDMA system can deploy radio technology like the Global System for Mobile Communications (GSM).
[0233] An OFDMA system can deploy radio technology such as Ultra-Mobile Broadband (UMB), Evolved UTRA (E-UTRA), Institute of Electronic Engineers and Electricians (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE and LTE-A are versions of UMTS that use E-UTRA. UTRA, E-UTRA,
Petition 870190114669, of 11/08/2019, p. 114/172
110/117
UMTS, LTE, LTE-A, NR and GSM are described in documents from the organization called Partnership Project of the 3rd generation (3GPP). CDMA2000 and UMB are described in documents from an organization called Partnership Project of the 3rd Generation 2 (3GPP2). The techniques described in this document can be used for the radio systems and technologies mentioned above as well as other radio systems and technologies. Although aspects of an LTE or NR system can be described for purposes of example, and LTE or NR terminology can be used in much of the description, the techniques described in this document are applicable in addition to LTE or NR applications. .
[0234] In LTE / LTE-A networks, including such networks described in this document, the term evolved node B (eNB) can be used in general to describe base stations. The wireless communications system or systems described in this document may include a heterogeneous LTE / LTE-A or NR network in which different types of eNBs provide coverage for various geographic regions. For example, each eNB, next generation NodeB (gNB), or base station can provide communication coverage for a macrocell, a small cell, or other types of cell. The term cell can be used to describe a base station, a carrier or component carrier associated with a base station, or a coverage area (eg, sector, etc.) of a carrier or base station, depending on the context.
[0235] Base stations may include or may be referred to by those skilled in the art as a
Petition 870190114669, of 11/08/2019, p. 115/172
111/117 transceiver base station, a radio base station, an access point, a radio transceiver, a NodeB, eNodeB (eNB), gNB, Domestic NodeB, a Domestic eNodeB or some other suitable terminology. The geographic coverage area for a base station can be divided into sectors that make up only a portion of the coverage area. The wireless communication system or systems described in this document may include base stations of different types (for example, macro or small cell base stations). The UEs described in this document may be able to communicate with various types of base stations and network equipment, including macro eNBs, small cell eNBs, gNBs, relay base stations and the like. There may be overlapping geographic coverage areas for different technologies.
[0236] A macrocell generally covers a relatively large geographical area (for example, several kilometers in radius) and can allow unrestricted access by UEs with service subscriptions with the network provider. A small cell is a base station with low power compared to a macrocell, which can operate in the same or different frequency bands (for example, licensed, unlicensed, etc.) as macrocells. Small cells can include picocells, femtocells and microcells, according to several examples. A picocell, for example, can cover a small geographical area and can allow unrestricted access by UEs with service subscriptions with the network provider. A femtocell can also cover a small geographical area (for example, a residence) and,
Petition 870190114669, of 11/08/2019, p. 116/172
112/117 can provide unrestricted access by UEs that have a femtocell membership (for example, UEs in a closed subscriber group (CSG), UEs for users in the home, and the like). An eNB for a macrocell can be referred to as an eNB macro. A small cell eNB can be referred to as a small cell eNB, an eNB peak, an eNB femto, or a domestic eNB. An eNB can support one or multiple (for example, two, three, four and the like) cells (for example, component carriers).
[0237] The wireless communication system or systems described in this document can support synchronous or asynchronous operation. For synchronous operation, base stations can have a similar frame or timing, and transmissions from different base stations can be roughly aligned in time. For asynchronous operation, base stations may have a different frame or timing, and transmissions from different base stations may not be time aligned. The techniques described in this document can be used for any of the synchronous or asynchronous operations.
[0238] The downlink transmissions described in this document can also be called forward link transmissions, while the uplink transmissions can also be called reverse link transmissions. Each communication link described in this document including, for example, wireless communication system 100 and 200 of Figures 1 and 2 can include one or more carriers, where each carrier can be a signal made up of multiple subcarriers
Petition 870190114669, of 11/08/2019, p. 117/172
113/117 (for example, waveform signals of different frequencies).
[0239] The description set out in this document together with the accompanying drawings describes exemplary configurations and does not represent all examples that can be deployed or that are within the scope of the claims. The term exemplary used in this document means that it serves as an example, occurrence or illustration, and not preferential or advantageous over other examples. The detailed description includes specific details for the purpose of providing an understanding of the techniques described. These techniques, however, can be practiced without these specific details. On some occasions, well-known structures and devices are shown in the form of a block diagram in order to avoid obscuring the concepts of the examples described.
[0240] In the attached Figures, components or similar resources may have the same reference label. In addition, several components of the same type can be distinguished by following the reference label by a dashed line and a second label that is distinguished from similar components. If only the first reference label is used in the specification, the description is applicable to any of the similar components that have the same first reference label independent of the second reference label.
[0241] The information and signals described in this document can be represented using any of a variety of technologies and techniques
Petition 870190114669, of 11/08/2019, p. 118/172
114/117 different. For example, the data, instructions, commands, information, signals, bits, symbols and chips that can be referenced throughout the description above can be represented by voltages, currents, electromagnetic waves, magnetic fields or by particles, optical fields or particles, or any combination thereof.
[0242] The various blocks and illustrative modules described in conjunction with this disclosure can be deployed or performed with a general purpose processor, DSP, ASIC, FPGA or other programmable logic device (PDL), discrete gate or logic transistors, discrete hardware components or any combination of them designed to perform the functions described in this document. A general purpose processor can be a microprocessor, but alternatively, the processor can be any processor, controller, microcontroller or conventional state machine. A processor can also be deployed as a combination of computing devices (for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors together with a DSP core, or any other such configuration).
[0243] The functions described in this document can be implemented in hardware, software, performed by a processor, firmware or any combination thereof. If implemented in software executed by a processor, the functions can be stored or transmitted through one or more
Petition 870190114669, of 11/08/2019, p. 119/172
115/117 instructions or codes in a computer-readable medium. Other examples and other deployments are within the scope of the disclosure and attached claims. For example, due to the nature of the software, the functions described above can be implemented using software executed by a processor, hardware, firmware, physical connections, or combinations of any of these. The features that deploy functions can also be physically located in various positions, including being distributed so that portions of the functions are deployed in different physical locations. Also, as used in this document, including in the claims, or as used in a list of items (for example, a list of items pre-punctuated by an expression such as at least one among or one or more among) indicates an inclusive list of so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used in this document, the expression based on should not be interpreted as a reference to a closed set of conditions. For example, an example block that is described as based on condition A can be based on condition A and condition B without departing from the scope of the present disclosure. In other words, as used in this document, the expression based on must be constructed in the same way as the expression based, at least in part, on.
[0244] Computer-readable media includes both non-transitory computer storage media and communication media that includes any medium that
Petition 870190114669, of 11/08/2019, p. 120/172
116/117 facilitate the transfer of a computer program from one place to another A non-transitory storage medium can be any available medium that can be accessed by a general purpose processor or a computer for specific purposes. By way of example and without limitation, non-transitory computer-readable media may comprise RAM, ROM, electrically erasable programmable read-only memory (EEPROM), compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices or any other non-transitory medium that can be used to transport or store the desired program code media in the form of instructions or data structures and that can be accessed by a computer for general or specific purposes, or a general purpose or specific purpose processor. Also, any connection is properly called a computer-readable medium. For example, if the software is transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared , radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies like infrared, radio and microwave are included in the definition of medium. The magnetic disk and the optical disk, as used in this document, include CD, laser disk, optical disk, digital versatile disk (DVD), floppy disk and Blu-ray disk, in which magnetic disks normally reproduce data magnetically, while optical discs reproduce data
Petition 870190114669, of 11/08/2019, p. 121/172
117/117 optically with lasers. The combinations of the above are also included in the scope of computer-readable media.
[0245] The description in this document is provided to enable a person skilled in the art to reproduce or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined in this document can be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and projects described in this document, but must be in accordance with the broadest scope consistent with the innovative principles and resources disclosed in this document.

权利要求:
Claims (70)
[1]
1 . Method for wireless communication in a source mobility and access management (AME) function comprising:
determining that the currently allowed network slices supported for a user equipment (UE) based on at least part of a network trigger are modified;
identify recently allowed network slices supported for the UE based at least in part on the determination;
selecting a target AMF based at least in part on recently allowed network slices, where the target AMF is accessible by the source AMF; and trigger an MFA relocation based at least in part on selection.
[2]
A method according to claim 1, which further comprises:
determining that the UE has an instance of active network slice (NSI) associated with at least one network selection assistance information (NSSAI); and identifying that an active NSI is supported by the recently allowed network slices.
[3]
A method according to claim 2, which further comprises:
generate a progress report that indicates a status for all existing protocol data unit (PDU) sessions associated with the active NSI.
[4]
4. Method according to claim 2, wherein the triggering of the MFA relocation comprises
Petition 870190114669, of 11/08/2019, p. 123/172
2/26 additionally:
transmit a relocation request from
AMF for the target AMF based at least in part on recently allowed network slices, where the AMF relocation request comprises a status of all existing PDU sessions associated with the active NSI that are supported and active, or an identifier globally exclusive temporary (GUTI) new radio (NR), or both.
[5]
A method according to claim 1, which further comprises:
trigger a procedure for releasing an active PDU session associated with the currently allowed network slices based at least in part on the identification that the active PDU session is not supported by the recently allowed network slices.
[6]
6. Method according to claim 5, in which the triggering of the release procedure is based, at least in part, on direct signaling to the UE.
[7]
7. Method for wireless communication in a target access and mobility management (AMF) function that comprises:
receive, from a .AMF-source, an AMF relocation request for user equipment (UE) currently served by the source AMF, the AMF relocation request comprising recently allowed network slices and UE context information ;
allocate an updated identifier based at least in part on the AMF relocation request; and transmit to the UE a configuration request message comprising the identifier
Petition 870190114669, of 11/08/2019, p. 124/172
3/26 updated, an updated status of an existing protocol data unit (PDU) session, or the recently allowed network slices, or a combination thereof.
[8]
8. Method according to claim 7, wherein the updated identifier comprises a globally unique temporary identifier (GUTI) of new radio (NR).
[9]
9. Method according to claim 7, wherein the UE context information comprises a situation of one. existing PDU session associated with an active network slice (NSI) instance or a current NR GUTI, or a combination thereof.
[10]
10. Method for wireless communications on user equipment (UE) comprising:
receive, from a source mobility and access management (AMF) function, a configuration message comprising an identifier associated with a target AMF, a. status of existing active protocol data unit (PDU) sessions of the UE, or recently allowed network slices, or a combination thereof;
store information associated with the recently allowed network slices and identifier;
identify an active PDU session based at least in part on the status of the existing active PDU sessions of the configuration message, where the active PDU session is not supported by the recently allowed network slices; and locally release the active PDU session.
[11]
A method according to claim 10, wherein the identifier comprises a temporary identifier
Petition 870190114669, of 11/08/2019, p. 125/172
4/26 globally exclusive (GUTI) of new radio (NR).
[12]
12. Method for wireless communication in a source mobility and access management (AMF) function comprising:
determining that if modified, the currently allowed network slices used by a UE on the basis of at least part of a received network trigger;
identify recently allowed network slices for the UE with. based at least in part on the determination; and determine that a target AMF associated with the recently allowed network slices is inaccessible by the AMF source.
[13]
A method according to claim 12, which further comprises:
transmit a deregistration request to the UE based at least in part on the determination that the target AMF is inaccessible by the source AMF.
[14]
14. Method according to claim 13, in which the deregistration request comprises an indication to perform a re-registration procedure, the recently allowed network slices, or a code indicating that the deregistration request responds a change in supported network slices, or a combination of them.
[15]
A method according to claim 13, which further comprises:
trigger a procedure for releasing an active protocol data unit (PDU) session
Petition 870190114669, of 11/08/2019, p. 126/172
5/26 associated with currently allowed network slices that are not supported by recently erased network slices; and release the UE context comprising an active PDU session progress report or a new radio globally unique temporary identifier (GUTI) (NR), or both based at least in part on the d and s and n and d.
[16]
16. Method for wireless communications on user equipment (UE) comprising:
identify a re-registration request and a code indicating a request to register a set of network slices associated with a recently allowed network slice based at least in part on a deregistration request received from a management and access role (AMF) source serving the UE;
identifying recently allowed network slices based on at least part of the unregistration received; and generate a request to register the set of network slices based at least in part on the code.
[17]
17. Method, according to. claim 16, which further comprises:
store information associated with recently allowed network slices, where the information comprises NSSAI.
[18]
18. Method for wireless communication in an access network (AN) comprising:
receive, from a user equipment (EU), a
Petition 870190114669, of 11/08/2019, p. 127/172
6/26 radio resource control (RRC) connection request comprising network slice selection assistance information (NSSAI);
identify a source management and access function (MFA) associated with the currently allowed network slices of the UE based at least in part on. NSSAI;
determine that the NSSAI be modified based at least in part on a trigger indication; identify recently allowed network slices supported for the UE based at least in part on the determination;
select a target MFA to serve the UE based at least in part on the recently allowed network slices; and trigger an AMF relocation based at least in part on the selection, where the AMF relocation comprises signaling the source AMF to redirect soli.cj. connection cup o and R.nC for, the AMF — a. 1 vo.
[19]
19. Method according to claim 18, wherein the signaling of the source AMF comprises: transmitting an indication comprising information for the selection of the target .AMF to redirect the RRC connection request; and transmit instructions to perform the redirection through the source AMF.
[20]
20. Method according to claim 19, in which the instructions for performing the redirection correspond to the signaling between the _AMF-source and the AMF-target by means of AN.
[21]
21. The method of claim 19, in.
Petition 870190114669, of 11/08/2019, p. 128/172
7/26 that the instructions for performing the redirection correspond to the signaling between the source AMF and the target AMF by means of direct signaling.
[22]
22. The method of claim 18, wherein the trigger indication comprises a policy control function (PCF) indication, one. indication that designates a change to a subscription to one or more currently allowed network slices, or a combination thereof.
[23]
23. Method, according to. claim 18, which further comprises:
establish an N2 signaling connection with the target AMF; and transmit a NAS message received from the UE to, the target AMF using the. N2 signaling connection.
[24]
24. The method of claim 23, which comprises additionals:
transmit, to the source AMF, a request to release an N2 signaling connection.
[25]
25. The method of claim 23, which further comprises:
receive, from the target MFA, a globally unique temporary identifier (GUTI) of updated NR for the UE; and replace a previous NR GUTI with the updated NR GUTI received for the
HUH.
[26]
26. Method for wireless communication in an access network (AN) comprising:
receive, from the UE, a request for relocation of a source management and access function (AMF) associated with the currently allowed network slices of the UE with
Petition 870190114669, of 11/08/2019, p. 129/172
8/26 base at least in part on information from network slice selection assistance (NSSAI);
determine that the NSSAI be modified based at least in part on a trigger indication; identify recently allowed network slices supported for the UE based at least in part on the determination;
select a target MFA to serve the UE based at least in part on the recently allowed network slices; and triggering an MFA relocation based at least in part on the selection, where the MFA relocation comprises initiating a redirection of the UE from the source AMF to, the AMF — a. 1 vo.
[27]
27. Method, according to claim 26, was that the relocation request comprises context information by at least one of the recently allowed network slices, the UE, or the target MFA.
[28]
28. The method of claim 26, which further comprises:
receive, from the target MFA, a globally unique temporary identifier (GUTI) of updated NR for the UE; and replace a previous NR GUTI with the updated NR GUTI received for the
HUH.
[29]
29. Method, according to. claim 26, which further comprises:
transmit, to the UE, a configuration request message comprising the updated NR GUTI, a status of data unit sessions from
Petition 870190114669, of 11/08/2019, p. 130/172
9/26 UE's existing active protocol (PDU), indication of modification to. NSSAI, or a combination thereof.
[30]
30. The method of claim 26, wherein the trigger indication comprises a policy control function (PCF) indication, an indication that designates a change to a subscription to one or more currently allowed network slices , or a combination of ιϊϊ Θ SlTl ci. S "
[31]
31. The method of claim 26, in. that the redirection of the UE is based at least in part on an operator policy.
[32]
32. Wireless communication device comprising:
a p r o c e s s a do r;
memory in electrical communication with the processor; and instructions stored in memory and executable by the processor to make the device:
determine to modify the currently allowed network slices supported for a user device (UE) based at least in part on a network trigger;
identify recently allowed network slices supported for the UE based at least in part on the determination;
select a target AMF based at least in part on the recently allowed network slices, where the target AMF is accessible by the device; and trigger an MFA relocation based at least in part on the selection.
Petition 870190114669, of 11/08/2019, p. 131/172
10/26
[33]
33. Apparatus according to claim 32, wherein the instructions are additionally executable by the processor to cause the apparatus to:
determine that the UE has an active network slice (NSI) instance associated with at least one network selection assistance information (NSSAI); and identify that an active NSI is supported by the recently allowed network slices.
[34]
34. Apparatus according to claim 33, wherein the instructions are additionally executable by the processor to cause the apparatus to:
generate a progress report that indicates a status for all existing protocol data unit (PDU) sessions associated with the active NSI.
[35]
35. Apparatus according to claim 33, wherein the instructions for triggering the relocation of AMF are additionally executable by the processor to make the apparatus:
transmit an AMF relocation request to the target AMF based at least in part on the recently allowed network slices, where the AMF relocation request comprises a status of all existing PDU sessions associated with the active NSI that are supported and active, or a globally unique temporary identifier (GUTI) of new radio (NR), or both.
[36]
36. Apparatus, according to. claim 32, wherein the instructions are additionally executable by the processor to make the device:
trigger a procedure to release an active PDU session associated with the network slices currently
Petition 870190114669, of 11/08/2019, p. 132/172
11/26 allowed on a basis at least in part by the identification that the PDO session is active and not supported by the recently allowed network members.
[37]
37. Apparatus according to claim 36, wherein the instructions for triggering the release procedure are based at least in part on. direct signaling to the UE.
[38]
38. A wireless communication device comprising: a processor;
memory in electrical communication with the processor; and instructions stored in memory and executable by the processor to make the device:
receive, from a source mobility and access management function (AMF), an AMF relocation request for user equipment (UE) currently served by the source AMF, with the AMF relocation request comprising network slices recently allowed and EU context information;
allocate an updated identifier based at least in part on the AMF relocation request; and transmit to the UE a configuration request message comprising the updated identifier, an updated status of an existing protocol data unit (PDU) session, or the recently allowed network slices, or a combination thereof.
[39]
39. Apparatus, according to claim 38, was that the updated identifier · comprises a globally unique temporary identifier (GUTI) of new radio (NR).
Petition 870190114669, of 11/08/2019, p. 133/172
12/26
[40]
40. Apparatus according to claim 38, wherein the UE context information comprises one. situation of an existing PDU session associated with an active network slice (NSI) instance or a current NR GUTI, or a combination of them.
[41]
41. Apparatus for. wireless communication comprising: a processor;
memory in electrical communication with the p r o c e s a. ache; and instructions stored in memory and executable by the processor to make the device:
receive, from a source mobility and access management (AMF) function, a configuration message comprising an identifier associated with a target AMF, an existing active protocol data unit (PDU) session status of the device, or recently allowed network slices, or a combination thereof;
store information associated with the recently allowed network slices and identifier;
identify an active PDU session based at least in part on the status of the existing active PDU sessions of the configuration message, where the active PDU session is not supported by the recently sliced network slices; and release the active PDU session locally.
[42]
2. Aparerho 4, o a.cordo with reivind ..!. Ca.çao ^z 4.i. , where the identifier comprises a globally unique temporary identifier (GUTI) of new radio (NR).
[43]
43. Wireless communication device that
Petition 870190114669, of 11/08/2019, p. 134/172
13/26 comprises: a processor;
memory in electrical communication with the processor; and instructions stored in memory and executable by the processor to make the device:
determine that the currently allowed network slices used by a UE be modified based at least in part on a received network trigger;
identify recently allowed network slices for the UE based at least in part on the determination; and determine that a target MFA associated with the recently allowed network slices is inaccessible by the device.
[44]
44. Apparatus, o and in accordance with claim 45, in which the instructions are additionally executable by the processor to make the device:
forward a deregistration request to the UE based at least in part on.
determination that the target MFA is inaccessible by the device.
[45]
45. Apparatus according to claim 44 in. that the deregistration request comprises an indication to perform a re-registration procedure, recently allowed network slices, or a code indicating that the deregistration request responds to a change in supported network slices, or a combination of the same.
[46]
46. Apparatus according to claim 44, wherein the instructions are additionally executable by the processor to cause the apparatus to:
Petition 870190114669, of 11/08/2019, p. 135/172
14/26 trigger a procedure for releasing an active protocol data unit (PDU) session, associated with the currently allowed network slices that are not supported by the recently allowed network slices; and release the UE context comprising an active PDU session progress report or a new radio globally unique temporary identifier (GUTI) (NR), or both based at least in part on the s enc a d e amen t. The .
[47]
47. Apparatus for wireless communication comprising: a processor;
memory in electrical communication with the processor; and instructions stored in memory and executable by the processor to make the device:
identify a request for re-registration and a code indicating a request to register a set of network slices associated with a recently allowed network slice based at least in part on a deregistration request received from a management and access role (AMF) source that is serving the device;
identify recently allowed network slices based at least in part on the deregistration received; and generate one. request to, register the set of network slices with base at least partly in the code.
[48]
48. Apparatus according to claim 47 in. that the instructions are additionally executable by the
Petition 870190114669, of 11/08/2019, p. 136/172
15/26 processor make the device:
store information associated with recently allowed network slices, where the information comprises NSSAI.
[49]
49. Device for wireless communication. wire comprising: a processor;
memory in electrical communication with the processor; and instructions stored in memory and executable by the processor to make the device:
receive, from a user device (UE), a radio resource control connection (RRC) request that comprises network slice selection assistance information (NSSAI);
identify a source management and access function (AMF) associated with the currently allowed network slices of the UE based at least in part on the NSSAI;
determine that the NSSAI be modified based at least in part on a trigger indication; identify recently allowed network slices supported for the UE based at least in part on d. and t and r m. i n a tion;
select a target MFA to serve the UE with. at least partly based on recently sliced network slices; and trigger a relocation of MFA with. at least partly based on selection, where a. AMF relocation comprises signaling the source AMF to redirect the RRC connection request to the target AMF.
[50]
50. Apparatus according to claim 49,
Petition 870190114669, of 11/08/2019, p. 137/172
16/26 at. that the instructions are additionally executable by the processor to make the device:
transmit an indication that comprises information for the selection of the target AMF to redirect the RRC connection request; and transmit instructions to perform the redirection through the source AMF.
[51]
51. Apparatus according to claim 49, in. that the instructions are additionally executable by the processor to make the device:
establish an N2 signaling connection with the target AMF; and transmit a NAS message received from the UE to the. Target AMF using the N2 signaling connection.
[52]
52. Apparatus according to claim 51, wherein the instructions are additionally executable by the processor to cause the apparatus to:
transmit to a previous UE server AMF a request to release an N2 signaling connection.
[53]
53. Apparatus according to claim 51, wherein the instructions are additionally executable by the processor to make the apparatus:
receive, from the target AMF, a globally unique temporary identifier (GUTI) of NR updated to the UE; and replace a previous NR GUTI with the updated NR GUTI received for the
[54]
54. Apparatus for. wireless communication comprising:
a processor;
memory in. electrical communication with the
Petition 870190114669, of 11/08/2019, p. 138/172
17/26 p r o c e s a do r; and instructions stored in memory and executable by the processor to make the device:
receive, from the UE, a request for relocation of a source management and access (AMF) function associated with the currently allowed network slices from the UE based at least in part on the network slice selection assistance information (NSSAI);
determine that the NSSAI be modified based at least in part on a trigger indication; identify recently allowed network slices supported for the UE based at least in part on the determination;
select a target MFA to serve the UE based at least in part on the recently allowed network slices; and trigger an MFA relocation based on at least. part of the selection, where the MFA relocation comprises initiating a redirection of the UE from the source MFA to the target MFA.
[55]
55. Apparatus according to claim 54 in. that the instructions are additionally executable by the processor to make the device:
receive, from the target AMF, a globally unique temporary identifier (GUTI) of NR updated to the UE; and replace a previous NR GUTI with the updated NR GUTI received for, the
[56]
56. Apparatus according to claim 54, wherein the instructions are additionally executable by the processor to cause the apparatus to:
Petition 870190114669, of 11/08/2019, p. 139/172
18/26 transmit to the UE a configuration request message comprising the updated NR GUTI, one. status of existing active protocol data unit (PDU) sessions of the UE, indication of modification to the NSSAI, or a combination thereof.
[57]
57. Apparatus for. wireless communication comprising: means for determining the modification of the currently allowed network slices supported for a user equipment (UE) based on at least. part on a network trigger;
means for identifying recently allowed network slices supported for the UE based on at least. part in the determination;
means for selecting a target mobility and access management (AMF) function based at least in part on recently allowed network slices, where the target AMF is accessible by the device; and means for triggering an MFA relocation based at least in part on selection.
[58]
58. A wireless communication device comprising: means for, from a source mobility and access management (AMF) function, an AMF relocation request to one. user equipment (UE) currently served by the source AMF, with the AMF relocation request comprising recently allowed network slices and UE context information;
means to allocate an updated identifier based at least in part on the AME relocation request · θ
Petition 870190114669, of 11/08/2019, p. 140/172
19/26 means for transmitting a configuration request message to the UE comprising the updated identifier, an updated status of an existing protocol data unit (PDU) session, or recently allowed network slices, or a combination thereof.
[59]
59. Wireless communication apparatus comprising: means for receiving, from a source mobility and access management (AMF) function, a configuration message comprising an identifier associated with a target AMF, a situation of unit sessions. existing active protocol data (PDU) from the device, or recently allowed network slices, or a combination thereof;
means for storing information associated with the recently allowed network slices and identifier;
means for identifying an active PDU session based at least in part on the status of the existing active PDU sessions of the configuration message, where the active PDU session is not supported by the recently allowed network slices; and means for locally releasing the active PDU session.
[60]
60. Wireless communication apparatus comprising: means for determining the modification of currently permitted network slices used by a UE with. based at least in part on a received network trigger;
means for identifying recently allowed network slices for the UE based at least in part on the determination; and
Petition 870190114669, of 11/08/2019, p. 141/172
20/26 means to determine that a target MFA associated with the recently allowed network slices is inaccessible by the device.
[61]
61. Wireless communication device comprising: means for identifying a request for new registration and a code indicating one. request to register a set of network slices associated with a recently allowed network slice based at least in part on a deregistration request received from a source management and access function (AMF) serving the device;
means to identify the network slices recently allowed with. base at least on. part of the registration cancellation received; and means for generating a request to register the set of network slices based at least in part on the code.
[62]
62. Device for wireless communication. wire comprising: means for receiving a radio resource control connection (RRC) request from a user equipment (UE) comprising network slice selection assistance information (NSSAI);
means to identify a source management and access function (MFA) associated with the currently allowed network slices of the UE based at least in part on. NSSAI;
means to determine whether to modify the NSSAI based at least in part on an indication of d. and s and n. c to d e am and n. t o;
Petition 870190114669, of 11/08/2019, p. 142/172
21/26 means to identify recently allowed network slices supported for the UE based on at least part of the determination;
means for selecting a target MFA to serve the UE based at least in part on the recently allowed network slices; and means for triggering an MFA relocation based at least in part on selection, where the MFA relocation comprises signaling the. Source AMF to redirect the RRC connection request to AMFalvo.
[63]
63. A wireless communication device comprising: means for receiving a request from the UE to relocate one. source management and access (AMF) function associated with the currently allowed network slices of the UE based at least in part on the network slice selection assistance information (NSSAI);
means for det.erm.inar to modify the NSSAI based at least in part on a trigger indication;
means for identifying recently allowed network slices supported for the UE based at least in part on the determination;
means for selecting a target management and access function (AMF) to serve the UE based at least in part on the recently allowed network slices; and means to unleash one. MFA relocation based on at least part of the selection, where MFA relocation comprises initiating a redirection of the UE from the source AMF to the target AMF.
Petition 870190114669, of 11/08/2019, p. 143/172
22/26
[64]
64. Non-transitory computer-readable medium that stores code for wireless communication through a source mobility and access management (AMF) function, the code comprising instructions executable by a processor to:
determining that the currently allowed network slices supported for user equipment (UE) are modified based at least in part on a network trigger;
identify recently allowed network slices supported for the UE based at least in part on the determination;
select a target AMF based at least in part on the recently allowed network slices, where the target AMF is accessible by the source AMF; and trigger an MFA relocation based at least in part on selection.
[65]
65. Non-transitory computer-readable medium that stores code for wireless communication through a source mobility and access management (AMF) function, the code comprising instructions executable by a processor to:
receive, from a source AMF, an AMF relocation request for user equipment (UE) currently served by the source AMF, the AMF relocation request comprising recently allowed network slices and UE context information;
allocate an updated identifier based at least in part on the AMF relocation request; and transmit to the UE a message of
Petition 870190114669, of 11/08/2019, p. 144/172
23/26 configuration request comprising the updated identifier, an updated status, of an existing protocol data unit (PDU) session, or the recently allowed network slices, or a combination thereof.
[66]
66. Non-transitory computer-readable medium that stores code for wireless communication by a user equipment (UE), the code comprising instructions executable by a processor to:
receive, from a source mobility and access management (AMF) function, a configuration message comprising an identifier associated with a target AMF, a situation of existing active protocol data unit (PDU) sessions from the UE, or recently allowed network slices, or a combination thereof;
store information associated with the recently allowed network slices and identifier;
identify an active PDU session based at least in part on the status of the existing active PDU sessions of the configuration message, where the active PDU session is not supported by the recently sliced network slices; and locally release the active PDU session.
[67]
67. Non-transitory computer-readable medium that stores code for wireless communication through a source mobility and access management (.AMF) function, the code comprising instructions executable by a processor for:
determine to modify the currently allowed network slices used by an UE based on at least
Petition 870190114669, of 11/08/2019, p. 145/172
24/26 in part on a received network trigger;
identify recently allowed network slices for the UE based at least in part on the determination; and determine that a target .AMF associated with the recently allowed network slices is inaccessible by the AMF source.
[68]
68. Non-transitory computer-readable medium that stores code for wireless communication by user equipment (UE), the code comprising instructions executable by a processor to:
identify a re-registration request and a code indicating a request to register a set of network slices associated with a recently allowed network slice based at least in part on a deregistration request received from a management and access role (AMF) source serving the UE;
identify recently allowed network slices based at least in part on the deregistration received; and generate a request to register the set of network slices based at least in part on the code.
[69]
69. Non-transitory computer-readable medium that stores code for wireless communication over an access network (AN), the code comprising instructions executable by a processor to:
receive a radio resource control (RRC) connection request from user equipment (UE) that comprises selection assistance information
Petition 870190114669, of 11/08/2019, p. 146/172
25/26 network slice (NSSAI);
identify a source management and access function (AMF) associated with the currently allowed network slices of the UE based at least in part on the NSSAI;
determine that the NSSAI be modified based at least in part on. an. trigger indication; identify recently allowed network slices supported for the UE based at least in part on the d e t e r m i n a tion;
select a target management and access function (AMF) to serve the UE based at least in part on the recently allowed network slices; and trigger a relocation of MFA with. at least partly based on selection, where a. AMF relocation comprises signaling the source AMF to redirect the RRC connection request to the target AMF.
[70]
70. Non-transitory computer-readable medium that stores code for wireless communication over an access network (AN), the code comprising instructions executable by a processor to:
receive, from the UE, a request for relocation of a source management and access function (AMF) associated with the currently allowed network slices from the UE based at least in part on the network slice selection assistance information (NSSAI);
determine that the NSSAI be modified based at least in part on. an. trigger indication; identify recently allowed network slices supported for the UE based at least in part on d. and t and r m. i n a tion;
Petition 870190114669, of 11/08/2019, p. 147/172
26/26 select a target management and access function (AMF) to serve the UE based at least in part on the recently allowed network slices; and trigger an MFA relocation based on at least. part of the selection, where the MFA relocation comprises initiating a redirection of the UE from the source MFA to the target MFA.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112019023498A2|2020-05-19|relocation of mobility and access management | function in a change triggered by network of network slices supported by a user device

---

US10736028B2|2020-08-04|Network service configuration and selection using network slices

---

US10231250B2|2019-03-12|Policy communication via control plane signaling

---

US10841084B2|2020-11-17|Session management authorization token

---

US20180279400A1|2018-09-27|Mechanisms for establishing user plane connectivity for non-3gpp access

---

CN109716856A|2019-05-03|Light connection and autonomous mobility

---

BR112020002342A2|2020-09-01|positioning reference signaling based on uplink in multi-beam systems

---

US10735957B2|2020-08-04|Context preparation

---

BR112019011153A2|2019-10-01|uplink transmission parameter selection for random access initial message transmission and retransmission

---

BR112019014120A2|2020-03-31|SIGNAL SHUFFLE SEQUENCE TECHNIQUES FOR WIRELESS COMMUNICATIONS

---

BR112020016591A2|2020-12-15|DOWNLAY TRANSMISSION BEAM CONFIGURATION TECHNIQUES FOR WIRELESS COMMUNICATIONS

---

US10757754B2|2020-08-25|Techniques for securing PDCP control PDU

---

BR112020001642A2|2020-07-21|derivation of security key for transfer

---

BR112020002249A2|2020-08-04|uplink power control based on procedure

---

BR112019022187A2|2020-05-12|DRAFT REFERENCE SIGN FOR SLOT AGGREGATION

---

BR112020022880A2|2021-02-23|repetition-based transmission

---

BR112020002456A2|2020-07-28|techniques for regrouping radio link control in wireless systems

---

BR112019024032A2|2020-06-02|CHANNEL SCANNING AND SYNCHRONIZATION SIGNALING

---

BR112020005029A2|2020-09-15|techniques for signaling burst set patterns of sync signals

---

BR112020010728A2|2020-11-10|partition format indicator in frequency division duplexing

---

US20200404719A1|2020-12-24|Truncated identification indicators

---

WO2022047690A1|2022-03-10|Establishing a network slicing connection

---

WO2021237391A1|2021-12-02|Encrypting application identifiers

---

US20200356694A1|2020-11-12|Architecture for device ownership, data provenance, governance and trade

同族专利:

---

公开号 | 公开日

---

CN110915260A|2020-03-24|

---

KR20200005642A|2020-01-15|

---

TW201902277A|2019-01-01|

---

US20190239136A1|2019-08-01|

---

WO2018212964A1|2018-11-22|

---

JP2020520173A|2020-07-02|

---

US20180332523A1|2018-11-15|

---

US10264506B2|2019-04-16|

---

US10880806B2|2020-12-29|

---

US20210227444A1|2021-07-22|

---

CN110915260B|2021-12-28|

---

SG11201909117SA|2019-11-28|

---

EP3636004A1|2020-04-15|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

WO2014052750A2|2012-09-27|2014-04-03|Interdigital Patent Holdings, Inc.|End-to-end architecture, api framework, discovery, and access in a virtualized network|

---

EP3215953B1|2014-11-28|2019-02-20|Huawei Technologies Co. Ltd.|Systems and methods for providing customized virtual wireless networks based on service oriented network auto-creation|

---

DE112016004103T5|2015-09-11|2018-05-30|Intel IP Corporation|Slice-enabled radio access network architecture for wireless communication|

---

US10506489B2|2015-09-18|2019-12-10|Huawei Technologies Co., Ltd.|System and methods for network slice reselection|

---

CN108141756A|2015-09-29|2018-06-08|瑞典爱立信有限公司|Facilitate network slice management|

---

US10536946B2|2015-12-08|2020-01-14|Huawei Technologies Co., Ltd.|Method and system for performing network slicing in a radio access network|

---

WO2017096606A1|2015-12-11|2017-06-15|华为技术有限公司|Resource allocation method and slice allocation unit|

---

WO2017142362A1|2016-02-17|2017-08-24|엘지전자 주식회사|Method for transmitting/receiving location registration-related message in wireless communication system and apparatus for same|

---

US20190124508A1|2016-04-01|2019-04-25|IDAC Holdiings, Inc.|Methods for service slice selection and separation|

---

KR20170119296A|2016-04-18|2017-10-26|한국전자통신연구원|Method and apparatus for communicating based on network slicing|

---

US10142994B2|2016-04-18|2018-11-27|Electronics And Telecommunications Research Institute|Communication method and apparatus using network slicing|

---

EP3456090B1|2016-05-12|2021-03-31|Convida Wireless, Llc|Connecting to virtualized mobile core networks|

---

WO2018034924A1|2016-08-16|2018-02-22|Idac Holdings, Inc.|Network slice reselection|

---

JP2018054386A|2016-09-27|2018-04-05|富士通株式会社|Radio wave arrival direction estimation device and radio wave arrival direction estimation method|

---

CN109804671B|2016-11-04|2020-05-08|华为技术有限公司|Network switching method, device and related equipment|

---

EP3944642A1|2016-12-21|2022-01-26|Telefonaktiebolaget LM Ericsson |Support of circuit switched service in a 5g core network|

---

WO2018121880A1|2016-12-30|2018-07-05|Telefonaktiebolaget Lm Ericsson |Network slice selection|

---

US10397892B2|2017-02-06|2019-08-27|Huawei Technologies Co., Ltd.|Network registration and network slice selection system and method|

---

TWI655877B|2017-02-06|2019-04-01|財團法人工業技術研究院|User equipment registration method for selecting network slicing, and network controller and network communication system using the method|

---

WO2018145727A1|2017-02-07|2018-08-16|Nokia Technologies Oy|Control of user equipment initiated change of network slices in a mobile system using network slicing|

---

EP3586547B1|2017-02-24|2020-06-17|Telefonaktiebolaget LM Ericsson |Methods and apparatuses for handling slice selection data for a user|

---

US10736028B2|2017-03-20|2020-08-04|Qualcomm Incorporated|Network service configuration and selection using network slices|

---

JP2020510377A|2017-03-21|2020-04-02|ノキア テクノロジーズ オサケユイチア|Enhanced registration procedure in mobile systems supporting network slicing|

---

CN110583034B|2017-05-02|2021-03-23|华为技术有限公司|Method, system and apparatus for accessing and providing network slice in mobile communication network|

---

US10820185B2|2017-05-08|2020-10-27|Qualcomm Incorporated|Mobility between areas with heterogeneous network slices|

---

PL3425963T3|2017-05-09|2021-06-28|Huawei Technologies Co., Ltd.|Slice-based communications method and device|

---

US10264506B2|2017-05-13|2019-04-16|Qualcomm Incorporated|Enable a network-trigger change of network slices|US10362511B2|2016-05-17|2019-07-23|Lg Electronics Inc.|Method and apparatus for determining PDU session identity in wireless communication system|

---

US10736072B2|2016-11-27|2020-08-04|Lg Electronics Inc.|De-registration method in wireless communication system and apparatus therefor|

---

KR20180081969A|2017-01-09|2018-07-18|삼성전자주식회사|Method, and associated parameter for routing initial access request message of terminal in mobile communication|

---

US10764785B2|2017-03-07|2020-09-01|Htc Corporation|Device and method of handling network slice information|

---

WO2018195877A1|2017-04-27|2018-11-01|华为技术有限公司|Communication method, device and system|

---

US10582432B2|2017-05-04|2020-03-03|Comcast Cable Communications, Llc|Communications for network slicing using resource status information|

---

US10820185B2|2017-05-08|2020-10-27|Qualcomm Incorporated|Mobility between areas with heterogeneous network slices|

---

US10264506B2|2017-05-13|2019-04-16|Qualcomm Incorporated|Enable a network-trigger change of network slices|

---

WO2018219352A1|2017-06-02|2018-12-06|Fg Innovation Ip Company Limited|Methods, devices, and systems for service-driven mobility management|

---

CN109151940B|2017-06-16|2021-12-03|华为技术有限公司|DC-based switching method and device|

---

KR102336313B1|2017-06-19|2021-12-07|삼성전자 주식회사|Method and apparatus of network virtualization and session management|

---

US11153813B2|2017-08-11|2021-10-19|Comcast Cable Communications, Llc|Network slice for visited network|

---

US10764789B2|2017-08-11|2020-09-01|Comcast Cable Communications, Llc|Application-initiated network slices in a wireless network|

---

CN109548098A|2017-08-15|2019-03-29|华为技术有限公司|Conversation processing method and relevant device|

---

EP3846508A1|2017-10-09|2021-07-07|Comcast Cable Communications LLC|Policy control for ethernet packet data|

---

WO2019073977A1|2017-10-11|2019-04-18|Nec Corporation|Ue configuration and update with network slice selection policy|

---

US10855814B2|2017-10-20|2020-12-01|Comcast Cable Communications, Llc|Non-access stratum capability information|

---

WO2019098745A1|2017-11-19|2019-05-23|엘지전자 주식회사|Handover method in wireless communication system and apparatus therefor|

---

CA3026841A1|2017-12-08|2019-06-08|Comcast Cable Communications, Llc|User plane function selection for isolated network slice|

---

EP3729868A1|2017-12-22|2020-10-28|LenovoPte. Ltd.|Network slice selection assistance information configuration|

---

US10986506B2|2018-02-16|2021-04-20|LenovoPte. Ltd.|Network slice selection assistance information configuration|

---

US10548107B2|2018-03-29|2020-01-28|Apple Inc.|Delaying cellular re-registration during critical conditions|

---

US10944796B2|2018-09-27|2021-03-09|Palo Alto Networks, Inc.|Network slice-based security in mobile networks|

---

US10477390B1|2018-09-27|2019-11-12|Palo Alto Networks, Inc.|Service-based security per user location in mobile networks|

---

US10574670B1|2018-09-27|2020-02-25|Palo Alto Networks, Inc.|Multi-access distributed edge security in mobile networks|

---

US10531305B1|2018-09-27|2020-01-07|Palo Alto Networks, Inc.|Service-based security per subscription and/or equipment identifiers in mobile networks|

---

US10462653B1|2018-09-27|2019-10-29|Palo Alto Networks, Inc.|Service-based security per data network name in mobile networks|

---

CN112690021A|2018-10-01|2021-04-20|联想（新加坡）私人有限公司|Method and apparatus for determining whether to transmit network slice selection assistance information|

---

KR20200077259A|2018-12-20|2020-06-30|삼성전자주식회사|Apparatus and method for connetcting a network|

---

CN111565479A|2019-02-14|2020-08-21|华为技术有限公司|Communication method, device and system thereof|

---

US11197176B2|2019-11-06|2021-12-07|Oracle International Corporation|Methods, systems, and computer readable media for providing for policy-based access and mobility management functionselection using network slice selection assistance informationavailability information|

---

US11240855B2|2020-01-13|2022-02-01|Qualcomm Incorporated|Local area network client participation in a network slice|

---

CN113498128A|2020-04-02|2021-10-12|维沃移动通信有限公司|Redirection method, network side equipment and terminal|

---

WO2021252443A1|2020-06-09|2021-12-16|Intel Corporation|Enhancing ran ue id based ue identification in o-ran|

---

WO2022011665A1|2020-07-17|2022-01-20|Qualcomm Incorporated|Network slicing nssp/ursp and ue local configuration updating|

法律状态:
2021-10-19| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201762505904P| true| 2017-05-13|2017-05-13|

---

US15/963,654|US10264506B2|2017-05-13|2018-04-26|Enable a network-trigger change of network slices|

---

PCT/US2018/029932|WO2018212964A1|2017-05-13|2018-04-27|Relocation of access and mobility management functionupon a network-triggered change of network slices supported for a user equipment|

---